As before, if you can move to mod_wsgi and use its daemon mode try
that as first step. This will eliminate memory swapping issues and
other issues around startup cost of Apache child processes loading
Django. Also gives a more predictable environment in which can then
start doing testing as to
I am having a similar problem with super slow performance in my
production environment (Apache with mod_python). Does anyone have
suggestions of settings that I can try tweaking?
Graham has provided a lot of useful information earlier in the post,
but I am with Vernon in that I am unsure
Thanks for both of your replies. It looks like what I'm experiencing
isn't entirely abnormal and would also explain why the "first group of
concurrent requests" are slower.
That said, coming from the comparatively easy worlds of PHP/mod_php
and even Java and Tomcat, getting Django properly
On Jan 2, 2:17 pm, Jeff Anderson wrote:
> vernon wrote:
> > Hi everyone,
>
> > When I was first experimenting with Django on my local machine with
> > the bundled webserver, one of the things I was really impressed by was
> > the speed — everything was instantaneous.
vernon wrote:
> Hi everyone,
>
> When I was first experimenting with Django on my local machine with
> the bundled webserver, one of the things I was really impressed by was
> the speed — everything was instantaneous. Listing things in the DB,
> modifying and saving changes etc...
>
> I finally
Hi everyone,
When I was first experimenting with Django on my local machine with
the bundled webserver, one of the things I was really impressed by was
the speed — everything was instantaneous. Listing things in the DB,
modifying and saving changes etc...
I finally decided to deploy the
6 matches
Mail list logo