Active
Project:
Boost
Version:
6.x-1.x-dev
Component:
Expiration logic
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
22 Apr 2010 at 22:56 UTC
Updated:
22 Apr 2010 at 23:10 UTC
Right now too much stuff can get expired from the cache at once. This needs a better solution.
Comments
Comment #1
mikeytown2 commentedIdeas:
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).