Am interested in knowing what kind of resources, if any, the block cache module would put a strain on with a multisite installation. For example does increasing the number of cached items work mysql/php or a part of mysql/php harder to the point that it would be good to increase the memory allocated to certain things? For an individual site I'm sure it would have it's effect but I'm especially concerned about hooking up block cache for several sites on my server without knowing whether I should be beefing up other areas.

Thanks for any pointers.

Comments

jjeff’s picture

jjeff commented

I honestly haven't done any testing in this area. We've seen up to 15% faster page load times in some of our tests, but we haven't really experimented with the module in multisite installations. I can't imagine why it would not gain you a performance increase on a multisite installation though.

The only overhead for cached blocks is one call to Drupal's cache_get(), which makes just one call to the database, then the information is unserialized (a mildly PHP-intensive task) and then the data is displayed. Compare this with the complex operations and multiple database calls of the blocks provided by something like Tagadelic and you're definitely going to come out ahead!

Good luck and let me know what you find.

-j

Caleb G2’s picture

Caleb G2 commented

15% seems conservative based on what I'm seeing. ;)

The reason I asked was because I just started playing with my mysql settings on the same day that I installed this. As I noted in the handbook page I wrote about tuning mysql Drupal, at least the way I have it set up, seems particularly demanding in the tmp_table_size and table_cache areas. I've got a multi-site situation however so it is very hard for me to tease a lot of meaning from the aggragated performance benchmarks.

jjeff’s picture

jjeff commented
Status: Active » Fixed

Moving off radar.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)