Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
If one does neither use the cron clean up feature nor the built in crawler the boost_cache table is quite useless.
Disabling writes by using a blackhole table has improved the performance on our DB server quite a bit.
Comment | File | Size | Author |
---|---|---|---|
#3 | boost-609310.patch | 7.61 KB | mikeytown2 |
#1 | boost-609310.patch | 3.91 KB | mikeytown2 |
Comments
Comment #1
mikeytown2 CreditAttribution: mikeytown2 commentedThis is more of a feature request rather then a bug report.
Once the file is created, it will never be overwritten; editing a node will not remove the old file. boost_cache_expire() uses the database instead of glob when flushing a node on edit. Your current setup is on the edge if this is slowing down you DB.
Anyway here's a patch... Key part is inside boost_cache_set() disabling
If I get multiple requests for this (10+) or get paid, or if a better patch comes out I will commit it & support this feature request.
Comment #2
mikeytown2 CreditAttribution: mikeytown2 commentedThis might be of interest
#610198: Allow flush button to del a file if not in database
Comment #3
mikeytown2 CreditAttribution: mikeytown2 commentedThis isn't that painful to do actually... so here it is.
Comment #4
mikeytown2 CreditAttribution: mikeytown2 commentedcommitted