Hello Graham,
I'm using the simplest way to start the server:
web.run(urls, globals())
and flup figures out that it's used as FastCGI and does the right thing.
If it defaults to multi-threaded mode, I think that's what I wanted,
if lighttpd supports multiplexing with multi-threaded flup, because
this way I don't have to start that many processes. I'm not very sure
about how to replace runfcgi yet as I'm not calling it directly...
Sunday, December 9, 2007, 11:43:34 PM, you wrote:
> What is in code.py that you are using as the FCGI bridge to your
> application. If you are using runfcgi() from web.py, from reading code
> of flup, it will default to enable multiplexing.
> 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()
> In other words, looks like it will attempt to create multiple threads.
> If this is true, then that is why your virtual memory use is so high.
> For starters, instead of calling runfcgi(), use instead something
> like:
> import flup.server.fcgi as flups
> return flups.WSGIServer(func, multiplexed=False).run()
> Replace func with what you passed to runfcgi().
> See if that drops virtual memory usage.
> Someone else will need to step in an explain how flup works out how
> many threads to run when multiplexing is enabled as I don't know.
> 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
-~----------~----~----~----~------~----~------~--~---
