Hi guys,
It does seem that I designed it poorly for apache deployment.
Memcached seems like a good option. After trying it out, it's decently
faster than disk, but not quite as fast as memory from the same python
process, mostly because of the serialization overhead.
- Build from original data s
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://c
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
Hi all,
I'm running a project with a resource-intensive Django app which needs
to cache some data in memory. This means the first time it handles a
request it may take say 10s, but secondary requests take <1s. I'm
having trouble with deploying it with apache2 and mod_python, in the
sense that alt
4 matches
Mail list logo
