On 6/4/07, Andrew <[EMAIL PROTECTED]> wrote: > What are some ballpark memory figures (memory vs requests/sec or > concurrent connections) for people running django on Apache prefork w/ > mod_python? Would, say, 150 requests/sec for a 2GB memory allocation > seem reasonable?
As always: it depends. > I understand that each application is different, and each apache > deployment can be tuned for different needs; like I said, I'm just > trying to get a ballpark. The problem is that we don't know anything about the setup. Is the single physical machine doing Apache/mod_python, a media server and your database (and possibly caching as well)? Are any of those running on separate machines? What are your MaxClients and MaxRequestsPerChild? Which is a roundabout way of reiterating that there is no rule, or even rule of thumb, for "X amount of memory will serve X requests per second" -- the configuration of Apache, and the other services running on the machine (and hence competing for resources) can so drastically affect performance and resource consumption that there's simply no way to even give a ballpark figure. -- "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 -~----------~----~----~----~------~----~------~--~---
