>Just looking over the httperf command, Kuba used --num-calls=1 This would not >be an accurate real-world test because it creates a new connection for every >request whereas most >browsers span requests over only a few connections. >Nicholas Piel's test used --num-calls=10 for testing HTTP/1.1 servers.
>In my own test, the difference (on Windows) between 1 and 10 yields a ~2.5x >increase in requests per second. I don't have a readily accessible Linux >right now. Kuba, please run these >numbers again with --num-calls=10. my reality is a lot of concurrent connections with only one call. I did num-calls=1 on purpose. I needed this test because of a "thing" I am building and this thing MUST work like this. Although I will try num-calls10 as soon as I have access to my testing environment again > I'd be curious which version Nicholas Piel tested. I just fixed a > performance issue yesterday for linux. If he tested prior to that version > (1.0.2) then yes, it would appear much slower. he used 1.0.1 - I am almost sure because comments about Rocket came on his blog entry earlier than yesterday and he was writing about doing rocket benchmarks in past tense so my conclusion/feeling is that he tested the version with a bug. > Some other things to consider: > - Kuba, how many processor cores are on your test machine? Having more > processes than processors will hurt Rocket more than Cherrypy. of course 4 processor cores. I tried 8 processes over 4 processor cores and indeed there is no gain > - It seems that you are testing this against web2py (notice how all the > responses are 3xx), perhaps you should just test the servers themselves for > now. If that's not the case, may we see the invocation code? yes. although I am testing both with web2py, and same application for both. It is fair. I'm not comparing my benchmarks with those from Nicholas. My "thing" will run web2py so this is what interests me. > In the bigger picture, there are some other matters to consider: > - Who will likely run web2py with the build-in webserver? New users testing > things out or devs running relatively small jobs. This might not be true. My "thing" is not for users surfing through some web application..downloading.. having sessions.., it is about some voice over ip servers talking to my servers via xml-rpc. So, I may need embedded server(like rocket or cherrypy) in production because it could simplify cluster environment thank you for your time, Tim, Rocket code looks really impressive -- Kuba -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
