vbet_guestcache to big

[Ramses]

The vbet_guestcache may be a good idea but it is now several gigabyte big and several thousandths files. Was it intended to work this way?

[vBET]

Yes. It caches complete HTML output - just as written in parameter description. How much it will take depends on how big your forum is.

Please note that you can always set additional ignored pages, or just disable it completely it you do not have disc space.

[Ramses]

Sure I could disable it but I wanted to reduce the serverload. Maybe you could write in the acp settings that this can blow up server space, not everybody may have 25 gigs of space. Or better to find a way to reduce the size.

[vBET]

Not everybody needs even 1 GB for this. As I wrote cache size depends on forum size. It caches each possible forum page it if is not in ignored set. Small forums have small amount of pages. Big forums have more pages and also more resources.

Anyway - it is good idea to make people be more aware what does it mean that full HTML output will be cached and add there information that it can take lot of disc space.

About reducing size - we can add option to zip cache files. It will take more server resources when cache is written, but reading it and sending such response will be faster.
Also we can add scheduled task which will automatically remove files which are too old. At this moment we do not do this - if file is too old it is simply overwritten during next request.

I'm moving this thread to Feature Requests

[wowglider.de]

It would be absolutly easy:
add a option to cache only X gigabytes and then delete the ones wich get less often visited.

[wowglider.de]

Lol, after i installed the new version with cache i never looked how much its using until now:

Debian-50-lenny-64-minimal:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/md2 688G 80G 573G 13% /
tmpfs 4.0G 0 4.0G 0% /lib/init/rw
udev 10M 764K 9.3M 8% /dev
tmpfs 4.0G 0 4.0G 0% /dev/shm
/dev/md1 2.0G 86M 1.9G 5% /boot

LOL! Before my hdd was used with 8GiG! Thats "great", btw it seems it caches wrong files eg:
_attachment_php_attachmentid_3350.html
_blog_php.html
_blog_php_do_list_y_2009_m_10.html

I dont want to cache Blogs, Tags and Attachments Oo

[steve]

I dont want to cache Blogs, Tags and Attachments Oo

You can add them to the ignore option.

[vBET]

It would be absolutly easy:
add a option to cache only X gigabytes and then delete the ones wich get less often visited.

This is also an option. First we will implement scheduled cleaner and maybe zipper (have to investigate this approach), because keeping statistics will have some impact on performance and for us performance is one of key issues. Still - we will keep in mind also this solution if other will be not sufficient

[vBET]

You can add them to the ignore option.

Exactly - just add it ti ignored. Anyway thanks for note - we will add ignoring atachements and tags as default ignore configuration. Blogs are something which many users can have cached, so we will not add it as fedault - but we made it configurable exactly for such cases - you want something more to be ignored. So just ignore it!

[vBET]

Also I just figure out that we can hange files naming template and include in file name does it considers less relevant pages or not. This way every day when automatic cleaning will be started it will recognizes appropriatelly cache file time to live and will clean more files. The first idea was to clean everything if it is older than not relevant pages should be. Now we will clean relevant cache pages faster - so you will save additional disc space!