I didn't know about DjangoCerise - I'd rolled my own CherryPy-WSGI-Django wrapper. I've actually just switched back to mod_python for the application hosting (with nginx sat in front serving static files). CherryPy caused one too many bad gateway errors for me to be comfortable with it; mod_python and Apache at least stays up of its own accord.
When I was running CherryPy I had two instances up with nginx load-balancing between them; this is trivial to set up - the article here describes the approach I took:
Using nginx for static files and Apache/mod_python for dynamic content seems to be working great so far, but I haven't fully stress tested it yet. I'll write it up properly in a few days.
I see, that was the setup I originally wanted to use (Apache & mod_python + Nginx for static content) -- and I will probably use it when I get my VPS.
But no mod_python setup is also appealing because mod_python uses much RAM... Not sure how it is with CherryPys server...
BTW, on what Bytemark plan are you? How it's going? I'm planning for a Bytemark 160MB plan, or some plan from Johncompanies (Linux Basic or FreeBSD Mid-Level). Can't decide. I hope 160MB is enough for a few Django sites.
Anyway, thanks for your help, I'll be in the same boat in a few days (VPS), so it's appreciated.
Hello,
Any details on this? I'm very curious. I found DjangoCerise.
That solves the CheryPy part, but what about load-balancing?
Sime - 20th December 2006 13:48 - #
I didn't know about DjangoCerise - I'd rolled my own CherryPy-WSGI-Django wrapper. I've actually just switched back to mod_python for the application hosting (with nginx sat in front serving static files). CherryPy caused one too many bad gateway errors for me to be comfortable with it; mod_python and Apache at least stays up of its own accord.
When I was running CherryPy I had two instances up with nginx load-balancing between them; this is trivial to set up - the article here describes the approach I took:
http://trac.turbogears.org/turbogears/wiki/NginxIn tegration
Using nginx for static files and Apache/mod_python for dynamic content seems to be working great so far, but I haven't fully stress tested it yet. I'll write it up properly in a few days.
I see, that was the setup I originally wanted to use (Apache & mod_python + Nginx for static content) -- and I will probably use it when I get my VPS.
But no mod_python setup is also appealing because mod_python uses much RAM... Not sure how it is with CherryPys server...
BTW, on what Bytemark plan are you? How it's going? I'm planning for a Bytemark 160MB plan, or some plan from Johncompanies (Linux Basic or FreeBSD Mid-Level). Can't decide. I hope 160MB is enough for a few Django sites.
Anyway, thanks for your help, I'll be in the same boat in a few days (VPS), so it's appreciated.
Sime - 20th December 2006 15:50 - #
I'm on the 160MB plan. It's been great apart from yesterday, which I'm pretty certain was down to my non-optimal configuration.
A "digg killed my site" post-mortem article would be rather interesting, I think. What kind of load does ~500 diggs result in, etc.