Forum OpenACS Q&A: Re: Some thoughts on OpenACS caching

Collapse
Posted by Brian Fenton on
Hi Gustaf

many thanks for the information - as always, very informative. I don't understand what you meant about "does not scale and leads to many locks. Flushing of this cache is brute-force or not happening at all." If we are not flushing, then this shouldn't be a problem, right? In the case where we are flushing, would it be a reasonable approach to use a different cache pool for each db-* call we want to cache? That will create a different ns_cache under the hood, right?

Does the util_memoize approach also have this problem?

Thanks for the code sample - sadly our OpenACS version doesn't have this feature.

I checked to see why we are running apm_get_installed_versions so much, and it looks like one of my colleagues added that in some custom code, so yes you are correct that it's not stock code.

Brian