Posted by Bacteria Man on November 3, 2009 at 1:18am
Jump to:
| Project: | Block Cache |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I have a legacy Drupal 5 web site that could benefit from block caching. I've considered using this module in the past, but the line in the last paragraph on the project page that read "...needs a few issues ironed out before an official release for D5..." always deterred me.
I'd be interested in hearing from users who have actively used this module and can attest its reliability. Thanks!
Comments
#1
Subscribing.
This has recently been installed on a D5 site of mine. I'll post back here if I find anything!
#2
It is used on www.pponline.co.uk which is a high traffic site (around 18,000 uniques a day).
We ran into a few issues when I enabled it on too many blocks (I had it set to per page / per user). The module kept doing SQL Deletes on the cache_block table where the index couldn't be used. This resulted in some very slow queries locking the table.
I restricted the block cache to just per-page for a few blocks and it's made a HUGE difference (particularly to the blocks which list the category pages - Sports, Topic & Training). These 3 blocks accounted for around 100 queries per page due to the url_alias lookups.
#3
nicholasThompson's experience reflects what mine was as well. This module is like salt: good in small quantities, but too many blocks in cache will generate more queries than you are saving.
So only enable it for a few very taxing blocks, and I think you'd be OK.