Turns it had nothing to do my web.py setup at all. I had a processing cluster that was opening lots of MySQL connections instead of only keeping one. It was a 1-line diff fix, heh.
Flup is actually very stable for the load I'm experiencing... Very nice. --Jonas Galvez On Apr 24, 4:13 pm, Sherwin Soltani <[email protected]> wrote: > On Mar 26, 4:37 am, Sebastjan Trepca <[email protected]> wrote: > > > Hi, > > > I have a site that handles about 100 req/sec on average, but sometimes > > it can get up to 500 req/sec and in that case flup spawns waaaay too > > many connections for system to handle so kernel kills the python > > process(too many open handles). > > Flup might be inadequate then. Perhaps you should migrate to using a > different server (like lighttpd or Apache). You can easily limit the > lighttpd thread count, and still manage to serve all your requests > adequately. > > > > > I'm using Nginx+flup+fastcgi+web.py0.31. > > > Could I use the integrated web server, spawn a few processes and just > > use nginx's proxy to point to them? > > Integrated server will be much slower and is not recommended for > deployment. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
