Posted by dkruglyak on February 16, 2007 at 10:58pm
Jump to:
| Project: | Block Cache |
| Version: | 4.7.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
Issue Summary
First, I want to say that this module is a real lifesaver.
However, the present challenge is identifying blocks that need caching. With large sites that could be a problem - I spent hours troubleshooting a production system brought to its knees by spiders hitting one particular block.
Perhaps the module should log block generation times for the original blocks to equip the admin with the list of "hot spots" to make caching tradeoff decision. Could this be feasible to implement?
Comments
#1
Hmmm... Interesting idea, but I'm not sure that there's really a way to do this.
The best thing is to turn on the query logging feature of the devel.module and take a look at what's happening "under the hood" for your site.
I'm really hoping that we can get (a variation of) blockcache into Drupal 6... this way authors would be able to "suggest" some caching options for their blocks. This should make things a lot simpler without all of the block copies, and other usability nasties.
In the meantime, I don't really think there's a way to do what you're asking for.
#2
I hear you. Maybe this belongs to devel module? It logs queries just fine, but there is a problem relating them to specific block - the level blockcache operates on...
Should this issue be reassigned to the devel module then?
#3
not part of devel ... see result_cache.module for an example of how to log times
#4
Clearing out old issues. No one is working on features.