It's for concurrency, since each of the requests takes a bit of time to process, in my case a few seconds or longer, I'm thinking if I start more Python, at least I can get the processing started. Otherwise, if there are many concurrent requests, they might be timed out by lighttpd without getting a chance to talk to the 10 Python back-end server, since they are all busy? In this particular project, one user can incur a few concurrent requests so theoretically, a dozen users will be able to DOS the server if each request takes long.
I got this understanding from my C FastCGI experience. The C FastCGI library does not support multiplexing on the connection to one FCGI server, as far as I remember. And the multi-threaded version is even slower than single threaded server. So essentially one FCGI server serves only one client at a time. And if each request takes a while to process, some requests will be timed out by web server. So I had to start a large number of FCGI server instances to be able to serve more concurrent users. This was true with the FastCGI server I wrote, and was also true with PHP working in FastCGI mode with lighttpd. I my previous load tests with PHP, if I didn't start enough number of PHP processes, user connections would start to drop when there were 100 or 200 concurrent requests. But maybe this is not true in lighttpd + web.py case. Does lighttpd multiplex the connection to web.py in multi-threaded mode? If so, I'd be glad to know it. I haven't done any load testing with this configuration so any real life experience would be helpful. But in any case, a Linux server not being able to run 20 Python processes sounds like a problem itself. I'm quite optimistic that a Windows server with similar configuration should run 20 Python fine. > 20 python processes looks too big. Can you tell me why are you using > so many processes? There could be a way to reduce that number. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
