Philip Mak wrote:
>
> The reason that I suggested a timestamp parameter (which means "regenerate
> the page if the cached copy is older than $timestamp") is that the
> Response->Include function would already have all the information it needs
> for this logic. It has the script filename, it has the key (e.g. query
> string), and it knows the timestamp of the cached file.
>
Let me mull this over some more.
> > The directive CacheSize, in bytes, already supports this. The same
> > cache size will be used for the XSLT cache, Includes/Script(TODO) cache,
> > and users cache(TODO). The default is 10000000, so using all three
> > caches could take nearly 30M. I don't want each to be specified
> > separately, there are already too many configs as it is.
>
> Wouldn't it be more intuitive if you made it so that all three caches
> added together can only take CacheSize bytes, rather than letting each
> individual cache take CacheSize bytes?
>
> The rationale for this is that when deciding what to set CacheSize to,
> someone would base this on how much disk space they have available. It's
> easier if they don't have to multiply by 3.
I can do this, but there will be more cache purging overhead
and I am not sure this is a good thing. Now, each DBM cache is checked
for its size only when used ... in this scenario, each DBM would be
checked for its size every request, increasing the stats x3 possibly,
depending on the number of caches used each request. The last policy
would be to only delete the cache if it fills up whenever
a STORE is done.
So, depending on the number of caches found, with your suggestion,
I would just take CacheSize / # of caches found per request
to be each cache's limit. This does make sense, but I don't like
the performance implications.
-- Josh
_________________________________________________________________
Joshua Chamas Chamas Enterprises Inc.
NodeWorks Founder Huntington Beach, CA USA
http://www.nodeworks.com 1-714-625-4051
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
