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/installfor the installation 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
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
