Apache is a multi process web server. Thus, more probable explanation is that the latter requests are being handled by a different Apache child process and thus those processes in turn need to load the data for the first time.
For an explanation of the different Apache MPM models see: http://code.google.com/p/modwsgi/wiki/ProcessesAndThreading This document relates to mod_wsgi, but except for daemon processes, it generally also applies to mod_python. If you need to have your application run in one distinct process so as to avoid this, you would need to use mod_wsgi daemon mode with one multithreaded process, or use mod_fastcgi with a similar configuration. Graham On Aug 15, 12:24 pm, "James Bennett" <[EMAIL PROTECTED]> wrote: > On 8/14/07, Lars <[EMAIL PROTECTED]> wrote: > > > My first thought was: I've missed a debugging flag somewhere that > > needs to be off. Here's what I roughly have: > > Have you checked the Apache directives which control how many requests > a process may server before it gets recycled? > > Remember that Apache processes do not live forever -- they serve a > certain maximum number of requests, then are killed and replaced by > new ones (which will, then, need to perform the same intensive > up-front calculation). If you need to permanently store something (or > at least, store it more permanently than what you're got now), try > memcached. > > -- > "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
