After further investigation I saw that memcached connections kept
adding up, until they reached the limit. From that point it got slow
and DB load jumped up. An Apache reload made everything fast again.
After googling for memcached connections or so, I found
http://groups.google.com/group/django-d
Oh, and I'm running exactly one Django site on the server.
--~--~-~--~~~---~--~~
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
On Oct 30, 11:30 am, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> Are you using Apache prefork MPM or worker MPM? If worker, how many
> threads in each process? Also, what do you have for maximum number of
> child processes in Apache configuration. Finally, how many Django
> instances are you hos
Graham Dumpleton napisał(a):
> BTW, does everyone use the pure Python memcached client module, ie.,
> memcache. Have seen comments to the effect that C client is three
> times faster, although if you then want object marshaling on top of
> that it would slow down a bit.
cmemcache still seems to
On Oct 30, 7:51 pm, web-junkie <[EMAIL PROTECTED]> wrote:
> Hi,
> I have a weird problem where I think memcached or caching in general
> might be the cause. I discovered it during testing the site with
> http_load. After a certain amount of fetches, or hits, to the server,
> the site does not re
Hi,
I have a weird problem where I think memcached or caching in general
might be the cause. I discovered it during testing the site with
http_load. After a certain amount of fetches, or hits, to the server,
the site does not respond normally. It takes 30 seconds or so. Strange
thing is: Only for
6 matches
Mail list logo
