Posted by mikeytown2 on April 22, 2010 at 10:56pm
Jump to:
| Project: | Boost |
| Version: | 6.x-1.x-dev |
| Component: | Expiration logic |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Right now too much stuff can get expired from the cache at once. This needs a better solution.
Comments
#1
Ideas:
Limit pager expiration example.com/?page=4. Only force the flushing of the first 5 pages and then the rest will expire over time so page 6 will expire before page 20. Limits and options configurable.
Look at views sort, if view places new content at end then don't flush entire stack; only flush that page.
Node edits - see if node has been removed from view; if yes then go ahead and do the pager expiration cascade; if not then only flush the page where the node lives.
Select views & views displays that should not be created in the relationship.
Optimize database operations for boost_cache_relationship table (it could use some help).
Only create a relationship entry if necessary. Frontpage view & node is promoted then no need for relationship (i think).