Recent Topics

1 Mar 10, 2015 16:24    

Soo my /cache folder grew as large as 9 GB. Which makes it hard for daily backups. So the question is, is it really worth it to have thousands of files total of 9GB, or should I disable cache completely ? Frankly I am inclined to disable it all together

2 Mar 10, 2015 23:15

Oh also, forgot to mention; the last time i tried to purge the cache, it almost crashed my server - dedi with quad core and 8gig ram.

Btw, I am still on 4.x install, dont know if performance was improved later on 5x

3 Mar 10, 2015 23:39

The cache folder prunes itself regularly since version... I don't know when, but I bet it's the version right after the one you use!

Also you should definitely exclude that folder from backups, no matter how big or small it is. The files it contains are only valid for 10 minutes! b2evolution won't use any of them if you restore them from a backup.

Finally, you can also delete the files from the command line without side effects.

4 Mar 11, 2015 01:41

Well I am on 4.1.3 to be exact but the cache folder is definitely not pruning itself. I couldnt be bothered keeping an eye on it, or setting custom rule for backup, so I have disable it completely for the time being. I dont know how much it'll effect the performance positively or negatively, will see.

2 things have been bugging me ever since, well 2 & a half. 1- stats, 2- cache, 2.5 - ajax forms (related to cache). Now that I have disabled cache completely, I have to find a way to do the same for stats. I mean having them is nice, but I could live without them, considering how much of a hassle they are (remembering emptying & optimizing hitlog table every once in a while).

I want to have my b2 install to be a true "set & forget", I dont want to be bothered with scheduled maintenance.

PS; I just tried deleting 1 day of stats, and it took literally 2 minutes to clear 1 day from the backoffice (45k hits). That sql query seems like it could use some optimizing, if it hasnt been optimized already.

@fplanque wrote earlier:

The cache folder prunes itself regularly since version... I don't know when, but I bet it's the version right after the one you use!

Also you should definitely exclude that folder from backups, no matter how big or small it is. The files it contains are only valid for 10 minutes! b2evolution won't use any of them if you restore them from a backup.

Finally, you can also delete the files from the command line without side effects.

5 Mar 20, 2015 19:06

1) You can disable all hit logging (stats) with a simple check box in the back office. Otherwise you can let it prune itself every night. Query is optimized in v5 (Do you see a pattern beggining to emerge?-

2) You can disable caches with check boxes too. Otherwise you can let the m prune themselves every night (v5).

2.5) Ajax forms are required when the pages are cached because otherwise we serve the same form to every user, including the same CAPTCHA to every user (to make it simple to understand. The problem is the same with CRUMBs which are sort of invisible captcha)

The summary is: uncheck the boxes or upgrade to v5 which is extremely stable by now and is compatible with v4 skins.

6 Apr 05, 2015 13:52

Where is that checkbox I gotta uncheck to disable all hit logging in admin ? I got no memory of it


Form is loading...