Thanks, got it.
I also set the stored_ sessions retention period to 5 days instead of 14 days.
Ive blocked a list of bots in .htaccess and the server disk space is no longer blowing out to 30Gig !
We had an issue where the /var/cache folder alone was 19GB!
I cant believe that even if every single page on our webstore was visited by a bot, that 19GB of cache would be created!
At least now we can try to update to the latest 4.3.?.
stored_sessions table has no correlation to the size of the cache.
The var/cache is impacted mostly by features, watermarks and languages.
If you have a graphic intensive site, using watermarks can become a huge part of your cache data.
Note that most of the space it taken up with directory structure rather than actual file content. I.e. there's a 5 level structure that contains 1 file that has 100bytes or so of data in it for ever watermarked image (detailed and thumbnail) in the system.
Intelligent use of features and only installing languages you expect to be used can also dramatically impact the cache size.
Disabling the search URL in robots.txt is probably the single most important thing you can do. But again, robots.txt is advisory, not compulsory. I.e.
Disallow: /*dispatch=products.search*Thanks very much for the advice, the size cache seems to be under control now.