On Thu, 2001-12-06 at 16:34, Aaron Straup Cope wrote:
> On 6 Dec 2001, Brian Wheeler wrote:
> 
> > On Thu, 2001-12-06 at 16:26, Sebastian Rahtz wrote:
> 
> > > it doesnt seem like it would take much to have this spiral
> > > up out of control? maybe you dont tinker with the stylesheets every
> > > day like I do :-}
> >
> > Well, this is our production machine, so we don't do much tinkering on
> > it.  We've got somewhere between 36-39,000 'virtual' pages (due to
> > selecting sections with path info, etc) on the site, so its really only
> > about 2x.  Since we allow users to log in (and that changes their
> > extra-info that axkit uses to determine the cache key), it could
> > theoretically grow forever.  Since we bought a ton of disk space,
> > numbers like these please the bean counters :)
> 
> Asks innocently : isn't this all a good candidate for a cron job? Speaking
> of which does anyone know, of the top of their head, whether AxKit locks
> cache files while they're being written?
> 

It might be a good candidate, but it boils down to the tradeoff with
using a cache in the first place:  is the disk space used worth the gain
in response time?  In our case, some of our documents are pretty good
size...and if the cache file gets wiped, it may take 20s or more to
rerender the page -- and this is on a dual PIII/866.  So its in our
interest to keep the cache files around, just for some of those nasty
files.  A file in particular which behaves this way is our college
profiles' alphabetical index.  Its 233K of XML and contains <item> tags
for 2844 schools...each containing 2 tags...so there are alot of tags
which have to be processed with this little monster comes up.

Thank god these files are bulk generated :)

Brian


> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to