Auto Clear System Cache

[Craig]

Any plans to create a scheduled task to clear system cache automatically?

[In Omnibus]

You wouldn't want the system to clear the cache automatically.

[Craig]

Give me reasons why not?

[In Omnibus]

Give me reasons why not?

The purpose of caching is to store data locally so that the web server does not have to call data from every resource on every page every time a page is loaded. If you clear the cache automatically your site will slow down considerably every time the cache is cleared unless you have no content and no activity.

[Craig]

But what about a site on a shared server that gets timeouts due to memory load?

If a site is on a vps there isn’t so much an issue, but even then there is a performance boost when cache is cleared.

[Wayne Luke]

But what about a site on a shared server that gets timeouts due to memory load?

There there is a bug and the system should be repaired. The Cache should be self replenishing. There is actually code that should be deleting old keys and replacing them with new ones on a regular basis. It shouldn't need to be cleared out.

What is the memory limit you have the system set to? We test at 64 MB and larger sites (millions of nodes) probably need more.

What is the the specific out of memory error that you're getting on the screen?

[Craig]

What is the memory limit you have the system set to? We test at 64 MB and larger sites (millions of nodes) probably need more.

What is the the specific out of memory error that you're getting on the screen?

I’ll need to check when I get home.

there is no message other than the site is not accessible.

[Craig]

I answered my own question, I think.

The host would block the website once it reached whatever memory limit it had set in place (I assume clear syscache provided some relief from that load). I do not know the setting as it was something they had in place to protect the other sites on the same server. The site in question has been moved to a managed vps, which gives insight to more server resource usage.

Furthermore I did not realize there was a memory limit built into the syscache and that it refreshed with newer content.

My apologies if my response in post #3 was curt.

[In Omnibus]

It's not a problem. Just because I'm trying to help doesn't mean I'm being any help.

[Wayne Luke]

Furthermore I did not realize there was a memory limit built into the syscache and that it refreshed with newer content.

It doesn't actually. The entire CACHE isn't loaded with every page load. What is cached are Query Results so they don't need to be run again for XX minutes. After the time period, the cache results would expire and be replaced with new results.

Since every user has an entirely different view of the site depending on their usergroup(s) and permission(s), the stored cache can get quite large. Customization of your site will dictate how large the cache can grow. By customization I mean modules (including options and permissions), usergroups and their permissions, plus channels and their permissions. It isn't relative to style customization.

[BirdOPrey5]

While it shouldn't be needed, I do have a scheduled task to do it in VB 5.x - https://www.vbulletin.org/forum/showthread.php?t=327063