As I talked in the last posts, the hello world application was run under apache/mod_wsgi. "I just tested with mod_wsgi under apache and the requests/second is about 1,500 with a hello world application. "
Please refer to the 3rd post for the details. On May 25, 12:02 pm, Graham Dumpleton <[email protected]> wrote: > On May 25, 1:41 pm, 柯甫敬 <[email protected]> wrote: > > > For the performance bottlenecks on my application side, I think I could have > > a couple of ways to optimize. You could regard it as a simple hello world > > application for now. My real question actually was "is it possible for > > lighttpd/fastcgi/webpy to support up to 1,000 requests/second for a simple > > hello world application"? I think increasing the threads limit in webpy > > could help, but I didn't find where to set or change in webpy. Can anyone > > help on this? > > What does a hello world program using web.py on Apache/mod_wsgi yield? > If you can't even get 1000 requests per second on Apache/mod_wsgi, > which is already proving to yield better performance than your fcgi > setup, then unlikely that even if fcgi is tuned that you will achieve > anything better. > > Even though lighttpd or nginx may be faster than Apache for yielding > static files, flup when used with fcgi adds a fair bit more overhead. > End result is that more often that not, a fcgi/flup application will > run slower than Apache/mod_wsgi. That is why Apache/mod_wsgi is a good > reference here as is close to maximum you can expect to get without > starting to load balance across multiple boxes etc. > > Graham > > > > > Thanks in advance. > > 2009/5/25 Tim <[email protected]> > > > > Thanks Graham. > > > My application is actual an ad serving application. I just tested with > > > mod_wsgi under apache and the requests/second is about 1,500 with a hello > > > world application. > > > It looks like a problem with fcgi then. How do you think? > > > 2009/5/25 Graham Dumpleton <[email protected]> > > > >> On May 25, 12:08 pm, Tim <[email protected]> wrote: > > >> > I'm recently porting an apache module to be webpy/fcgi/lighttpd based > > >> > application, but the performance doesn't look like good. > > > >> > With the apache module writen in C, it was able to process up to 2,000 > > >> > requests per second, however, when I ran a simple helloworld > > >> > application with webpy/fcgi/lighttpd, the server was processing about > > >> > 300 requests per second. > > > >> > I was followinghttp://webpy.org/installfortheinstallation and > > >> > default lighttpd configurations. I'm new to lighttpd and webpy, so I'm > > >> > wondering if there are any configuration options in lighttpd/webpy to > > >> > tune the performance to make the requests/second to be more than > > >> > 1,000? Also, is there any way to increase the threads limit in webpy > > >> > since when I tested with more than 120 concurrent users I would get > > >> > "backend is overloaded" errors? > > > >> What does your application do? Without knowing that, it is very hard > > >> to comment on whether your problems may actually be in your > > >> application, the fastcgi bridge, or your web server. > > > >> You should perhaps create a simple WSGI hello world program that > > >> doesn't even use web.py and determine how many requests that can > > >> handle. You might also as comparison to gauge whether the web server > > >> and/or fastcgi is the issue, compare that to WSGI hello world program > > >> under Apache/mod_wsgi on same system. > > > >> Graham- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
