On 5/16/07, Ray Dookie <[EMAIL PROTECTED]> wrote: > I'm interested to know how much load can a django box say with 512MB > ram handle.
The biggest question to ask here is what level of traffic you're expecting, and how quickly you expect that traffic to go; there are lots of things you can do to your setup to optimize for different traffic levels, so it's very hard to give a concise answer to "what can this server handle". Generally your biggest RAM sinks are going to be (not necessarily in this order): * memcached, if you're using it * Apache/mod_python, if you opt for that as the web server setup * Your database server For most situations, focus first on how much RAM you give to the database, because the database is almost always the first bottleneck in scaling (and because a huge memcached instance with a blazing-fast web server is no good if you can't get at the data to put it in the cache), then look at other concerns. If memory is a significant concern, you may also want to look at using lighttpd and FastCGI; lighttpd isn't always the ideal choice, but you can squeeze a little extra performance out of it by taking advantage of its relatively low memory use compared to Apache with prefork MPM (though bear in mind that you'll still have memory overhead from FastCGI processes). -- "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 [email protected] 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 -~----------~----~----~----~------~----~------~--~---
