On Mon, Jun 04, 2007 at 09:19:05AM -0000, Andrew 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?
I can't really help with figures, but for memory there are two good rules of thumb: * get twice as much as you think you need * get even more if you can afford it Memory is *often* the most important thing for increasing performance. If you don't really understand high scale performance tuning, it's a very good place to start - modern operating systems are pretty good at transparently taking advantage of more memory. I wouldn't build a web server with less than 4G of memory; I'd be staggered if that won't be able to cope with 150 reqs/second, but the limiting factors there are going to include the length of time taken per request, how much database interactivity there is (and what the concurrency capabilities of your database are), and various tuning parameters in apache such as MaxRequestsPerChild. James -- /--------------------------------------------------------------------------\ James Aylett xapian.org [EMAIL PROTECTED] uncertaintydivision.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
