Re: Scaling django (nginx + apache + mod_wsgi + postgresql)

Just to chime in on this.. In terms of commercial options, we have sometimes gone with ZXTM (now known as StingRay Traffic Manager) , it has some truly amazing features and you should definitely check it out. I believe that RiverBed have since started issuing free commercial licences for up to a

Re: Scaling django (nginx + apache + mod_wsgi + postgresql)

On Tue, Oct 30, 2012 at 7:35 AM, Isaac XXX wrote: > Hi Tom, > > you're right, I was not really explicit about what were my lacks of > information. Right now, the following points are the ones I can't found a > howto for the desired deployment: > > - Create a master-slave system

Re: Scaling django (nginx + apache + mod_wsgi + postgresql)

The easiest thing I've found to use is simply uWSGI with Nginx. It's easy to just create new Django servers on the fly. You simply include the IPs in a list and it will use various algorithms (optional) to distribute the requests appropriately. As a lot of applications are IO bound, you could

Re: Scaling django (nginx + apache + mod_wsgi + postgresql)

Hi there, maybe you're right, but I'm not really worried about RAM footprint, or resources consumption. I'm concerned now on architecture, setting a right scalable system, and a right cluster of systems, without lacks of communications between them. Underlaying technologies can be easily

Re: Scaling django (nginx + apache + mod_wsgi + postgresql)

Thank you so much for tips. I will keep them when I start to test environment for performance. Cheers Isaac On 10/29/2012 06:44 PM, Cal Leeming [Simplicity Media Ltd] wrote: Hi Isaac, If there is one thing I have learnt about scaling apps, it's about trying things out for yourself. Sure

Re: Scaling django (nginx + apache + mod_wsgi + postgresql)

Hi Tom, you're right, I was not really explicit about what were my lacks of information. Right now, the following points are the ones I can't found a howto for the desired deployment: - Create a master-slave system on postgresql, maintaining all systems up to date, distributing reads, and

Re: Scaling django (nginx + apache + mod_wsgi + postgresql)

The old rule of thumb is to avoid premature optimization. I'd build, profile, then scale or otherwise optimize as needed. This isn't a tutorial or really a discussion on all points of scaling a system; but identifying bottle necks will do wonders when it comes to deciding what, where, and how to

Re: Scaling django (nginx + apache + mod_wsgi + postgresql)

Hi Isaac, If there is one thing I have learnt about scaling apps, it's about trying things out for yourself. Sure there are some best practice guidelines (i.e. serving files from nginx, or using apache's X-SendFile rather than streaming out via the webapp), but if someone comes along and tells

Re: Scaling django (nginx + apache + mod_wsgi + postgresql)

On 29/10/2012 16:03, Isaac XXX wrote: Hi there, thank you for response Tom. Actually, I've a complete idea at how to build this system, but I lack the exact information about how to join systems, and what I was looking for was a source of cohesive information on all systems. At least, when

Re: Scaling django (nginx + apache + mod_wsgi + postgresql)

On Mon, Oct 29, 2012 at 4:03 PM, Isaac XXX wrote: > Hi there, > > thank you for response Tom. > > Actually, I've a complete idea at how to build this system, but I lack the > exact information about how to join systems, and what I was looking for was > a source of cohesive

Re: Scaling django (nginx + apache + mod_wsgi + postgresql)

Hi there, thank you for response Tom. Actually, I've a complete idea at how to build this system, but I lack the exact information about how to join systems, and what I was looking for was a source of cohesive information on all systems. At least, when I finish to build that system, I will

Re: Scaling django (nginx + apache + mod_wsgi + postgresql)

On Mon, Oct 29, 2012 at 2:42 PM, Isaac XXX wrote: > Hi folks, > > I'm developing a new application that should get high traffic. Right now, > I've other projects with the follow architecture: > > Nginx on front: serving static content and redirecting to apache for dynamic >

Scaling django (nginx + apache + mod_wsgi + postgresql)

Hi folks, I'm developing a new application that should get high traffic. Right now, I've other projects with the follow architecture: Nginx on front: serving static content and redirecting to apache for dynamic data Apache+mod_wsgi: serving dynamic pages PostgreSQL: backend for data storage