This is a good point -- why is that the default setting? From flup code: 946 Set multiplexed to True if you want to handle multiple requests 947 per connection. Some FastCGI backends (namely mod_fastcgi) don't 948 multiplex requests at all, so by default this is off (which saves 949 on thread creation/locking overhead). If threads aren't available, 950 this keyword is ignored; it's not possible to multiplex requests 951 at all.
A quick test with a lighttpd server shows a significant (40%) increase with this turned off. Someone correct me if I'm wrong, but the way I'm reading this is that it would handle multiple requests per client connection. This is probably not a common occurrence for most web apps since static content is usually served outside of fastcgi code path. Counter arguments? On Dec 7, 3:31 am, s7v7nislands <[email protected]> wrote: > hi,all! > any server support fastcgi 'mulitplexing', that allows a single > client-server connection to be simultaneously shared by multiple > requests? after google, I find apache,nginx,lighttpd all not support > it.and test with nginx, seem when mulitiplexed = False is faster than > True. > def runfcgi(func, addr=('localhost', 8000)): > """Runs a WSGI function as a FastCGI server.""" > import flup.server.fcgi as flups > return flups.WSGIServer(func, multiplexed=True, > bindAddress=addr).run() > > so why set this value 'True'? thanks! -- 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.
