Hi
This module generates up to 20,000 files in the cache every 2 - 3 days, which would be no problem if it was not leading to exceeding to the 50,000 inodes limit imposed by the webhost. When I manually empty the cache via the settings page, it drops to just under 30,000 & starts rapidly going up again.

A range of hosts that I would consider reasonable to host such a small community site with little traffic of mostly around 50/day (sharing an account with one other, non.Drupal site, which however has much more traffic but does not contribute much to this), seem to have the same 50,000 inode limit.

What can be done to either reduce this by automatic deletion after reaching some figure or considerably reducing this rapid growth, without affecting the performance of boost much?

Comments

alliax’s picture

alliax commented

It's the same for me, as I have over 100,000 nodes and 50,000 tags (I'm not using boost crawler, but still) and a lot of anonymous traffic, 2 files are generated per page with the .gz version, that's too much, what solution is there for this?

ghmercado’s picture

ghmercado commented

any updates?

bgm’s picture

bgm commented
Status: Active » Closed (won't fix)

In some cases, for example if you are using multiple Views pagers on one page, robots can loop on sections and cause a huge amount of static files to be created. You can check by manually inspecting the static cache, or using a tool such as "ncdu" to explore disk usage.

Otherwise, I'd say you have hit a limitation of boost (or of your hosting), since it is tied to the file system. A cache running purely in ram would probably clean old or least often accessed pages to free up resources, but doing that on the filesystem would be costly (and boost would probably end up just deleting pages all the time, and would not be easily able to know which pages are accessed more often)