David, slightly off-topic, but you should see some impressive gains if you move your static handling off Apache onto something lighter (Cherokee/Lighttpd/nginx/etc) and reverse-proxy the dynamic stuff through to a localhost-bound Apache.
Hell, I use Cherokee for dynamic content too (via django's SCGI output). Uses a tiny amount of resources compared to the Apache+mod_python setup I was using. On Wed, Mar 25, 2009 at 1:20 PM, David Holstius <david.holst...@gmail.com>wrote: > > We're migrating www.gigapan.org to Django (was: PHP/Smarty) on a page- > by-page basis. We have a high read/write ratio, so judicious caching > solves most of our scaling issues in the realm of dynamic web content. > Most of our stress comes from serving static imagery. So, let me > qualify that: we have Django running on some otherwise maxed-out > servers and it is performing extremely reliably. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
