Add Entity Cache module [#1793770]

The entity cache module was recommended as a method to allow caching for authenticated users. (http://drupal.org/project/entitycache). Should we investigate using this on commons since most caching mechanisms will not allow caching for authenticated users? Are there caveats to using this module? Can this be used in conjunction with other caching mechanism ( like a views cache)?

Most core entities will cache out of the box. For contrib, the module maintainer must use a EntityDefaultCacheController ( please verify the string ).

Comment	File	Size	Author
#5	commons-add_entitycache-1793770-5.patch	828 bytes	erikwebb

Comments

Comment #1

erikwebb commented 25 September 2012 at 13:56

I think this is a good option. Given the number of entities used throughout Commons (incl. nodes and lots of messages), I'd be curious the gain of this. I think #1792666: Use Views Content Cache to optimize performance should be a higher priority than this, but I'm not opposed to this in any way.

We should re-visit this once we have the full functionality implemented so that we can create quantifiable benchmarks.

Comment #2

crimsondryad commented 25 September 2012 at 22:37

We're in the process of starting to test this module on our (non-Commons) sites. When we get it installed on a high traffic one we'll capture the benchmarks and update this issue with results. One of our sites gets 3 million page views a month. Our DB traffic decreased 90% just by turning on anonymous page caching and Views caching. We're planning to use entity cache as an "AND" not an "OR". That site has some complex content types, so it may offer a decent view into what to expect.

Comment #3

erikwebb commented 26 September 2012 at 12:27

The complex content types will make the biggest difference, which Commons doesn't really have. I'm not opposed to this "AND" either, but just want to make sure it's worthwhile.

Comment #4

crimsondryad commented 27 September 2012 at 20:55

I asked KarenS about this, entity_cache will cache the entire entity object, which will make pulling ALL content / users more efficient. Views Content Cache will cache the html output. There isn't a conflict with using both modules and while many things will be pulled from Views, some things won't and this will cache most of those things.

Comment #5

erikwebb commented 2 October 2012 at 00:52

Title:	Caching using entitycache module	» Add Entity Cache module
Status:	Active	» Needs review

Status	File	Size
new	commons-add_entitycache-1793770-5.patch	828 bytes

It's absolutely an advantage. Anything we can do to optimize Commons out of the gate is great in my book, especially when it has no configuration or side effects. I'll go ahead and attach a patch here for argument's sake.

For the record - I recommend Entity Cache for all sites, but I'm just more cautious making sweeping recommendations for an entire distribution.