My motivation for developing Rocket wasn't speed as much as it was
concurrency. wsgiserver drops to 9% of its max throughput when
processing 25 concurrent connections and that drop continues downward as
more concurrent connections happen**. In contrast, Rocket drops to 53%
of its max at 25 concurrent connections and holds pretty steady around
that even as you get into 500 concurrent connections. I haven't had
enough patience to run a full test of wsgiserver at 500 concurrent
connections...it's painful.
I've got to put a disclaimer on that "fassimoster" though. There is one
instance where wsgiserver runs faster...that is with 1 active connection
for one request at a time (with no keepalive). All other scenarios run
faster. This is hardly a problem though because most of what we're
interested are browsers that use keepalive in order to pipe-line requests.
The purpose of Rocket is to make something more AJAX-robust. Version
0.2 is out today. Take a look if you like:
http://launchpad.net/rocket
I am still interested to know if anyone uses web2py without an external
webserver.
-tim
**YMMV - this is what I observed on my box.
On 1/8/2010 11:30 AM, mdipierro wrote:
I do not know what "fassimoster" means. I meant to type "faster" but
something weird happened to my editor window.
On Jan 8, 11:28 am, mdipierro<mdipie...@cs.depaul.edu> wrote:
The keepalive weirdness is gone when we upgraged to a more recent
version of wsgiserver. Some time ago. The only known limitation of the
current web server is failure of ssl for large uploads (and perhaps
downloads?). I run it in production.
Anyway, Tim, here is working on a new web server called Rocket that
will soon replace wsgiserver. It is much clearner and fassimoster.
massimo
On Jan 8, 10:13 am, Timbo<tfarr...@swgen.com> wrote:
I'm curious...how many of you use the built-in webserver (CherryPy's
wsgiserver) as opposed to Apache, LightTPD or Cherokee in web2py and
what do you use it for? If you don't know what I'm talking about,
you're probably using it.
I've used it in the past for both development on my desktop and
production. I switched to using mod_wsgi+Apache because of some HTTP-
keepalive wierdness (which has been discussed in the past). But if I
didn't have to rely on Apache, that would be one less thing to have to
worry about in our disaster recovery plan.
--
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.
