|Perl Monk, Perl Meditation|
Re: mod_perl sql result cacheby grantm (Parson)
|on Aug 23, 2011 at 08:47 UTC||Need Help??|
That really depends on your application/framework. mod_perl puts a persistent Perl interpreter inside each Apache process, so the values stored in global variables (or file scoped lexicals, or indeed anything that's still referenced) at the end of one request will still be there at the start of the next.
The problem with this raw mechanism is that the persistent/cached values exist separately in each Apache child process. Which means 1) you get multiple copies and 2) there's no way to invalidate a cached item across all processes.
It's usually better to use something like memcache to manage persistent cache values. It avoids the multiple copies issue and provides a central place to invalidate cached items.
So in summary, I'm afraid you'll have to dive into the code for your app to find out how it manages cached values.