Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is Object Caching? #115

Open
6 tasks
raamdev opened this issue May 5, 2016 · 0 comments
Open
6 tasks

What is Object Caching? #115

raamdev opened this issue May 5, 2016 · 0 comments

Comments

@raamdev
Copy link
Contributor

raamdev commented May 5, 2016


KB Article Creation Checklist
  • Write initial draft for this KB Article; label this issue draft and either questions or tutorials
  • Add required YAML configuration
  • Add Tags for this KB Article to the YAML config (see YAML Keys (Explained))
  • Edit and finalize draft for publishing (remove draft label, add draft-finalized label)
  • Assign Issue to yourself and create Markdown file (remove draft-finalized label, add pending)
  • Project Lead: Review and Publish KB Article (remove pending label, add published label)
Additional TODOs

Additional TODO list items go here.

title: What is Object Caching?
categories: questions
tags: 
author: raamdev
github-issue: 

[Referencing internal discussion with Jason where he describes the pros and cons of object caching, and explains what it is: https://websharks.slack.com/archives/comet-cache/p1462486001000589]

WordPress comes with its own Object Cache built-in (see WP Object Cache), as do many plugins for WordPress (including bbPress). The drop-in plugin file /wp-content/object-cache.php allows for a so-called Advanced Object Cache to take things a step further; e.g., caching transients into memory, and doing a persistent cache of what WordPress already deals with. We have not seen a single reliable implementation of an Advanced Objet Cache. Object caching that comes with WordPress already + Page caching with a plugin like Comet Cache is generally more than enough and the only scenario where it makes sense to add another layer of Advanced Object Caching is on completely custom, very high traffic WordPress sites where every single plugin and even the theme itself has been reviewed and tweaked to take advantage of the Advanced Object Cache (e.g., the NY Times blogs, which have a team of WordPress developers who tweak WordPress for high-availability).

Object caching is very specific to the PHP code itself (i.e., where the objects are created; the PHP code needs to take into consideration that the objects it creates might get cached). Many WordPress plugins are not written with object caching in mind, which is why adding Advanced Object Caching to a WordPress site with many different WordPress plugins often causes strange and seemingly mysterious issues. Larger and more well-maintained plugins like bbPress and BuddyPress are already written to take advantage of object caching, so adding another Advanced Object Cache will generally not produce any improvement in speed when it comes to those plugins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant