The inbuilt server is for development, not deployment. Why would you not just use lighttpd or nginx, free webservers that can more than handle your load?
Alec On Dec 2, 2009, at Dec 2, 2009 - 11:23 PM, Leon wrote: > hi, I am a newbie and using web.py for a service in interanet. > The qustion I'd like to ask is that how about the performance if I use > the built-in web server of web.py? > I found a post here long ago which said that: > " > I'm using web.py v0.1381 on a winxp machine. I tested it with > ApacheBenchmark tool. Using 1 concurrent connection, web.py would > server 200+req/sec. But if the concurrent connections grow to over > 100, > web.py can just handle ~20 req/sec. This is a huge performance > problem. > What can I do to make it better? As far as I know, web.py uses a > threaded-server. Will async server perform better in this case? > > " > Now,i am using web.py 0.32. > Is that true? If so, I think the build-in web server is suitable for > me. > > -- > > 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 > . > > -- 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.
