I will see if it works Thanks Justin On 5 ene, 04:37, Justin Davis <[email protected]> wrote: > Hi Bungow, > > web.py is multithreaded by default -- that is, a request comes in and > a new thread is spawned (or taken from a thread pool), and it handles > that request. If you've deployed this using fastcgi and nginx, then > flup is spawning the various threads. > > You can change this from a threaded fastcgi model to a pre-fork model > by changing the code in web/wsgi.py in def runfcgi. This is one way > to do it: > > def runfcgi(func, addr=('localhost', 8000)): > """Runs a WSGI function as a FastCGI server.""" > import flup.server.fcgi_fork as flups > return flups.WSGIServer(func, multiplexed=False, bindAddress=addr, > maxRequests=1000, debug=False).run() > > There isn't an official way to do this via configuration though, you > need to edit the file yourself. Otherwise I believe everything should > work as expected. > > -Justin > > On Jan 4, 1:33 pm, Bungow <[email protected]> wrote: > > > > > > > > > Hello,in first place, sorry for my english :) now Happy new year to > > everyone :P > > I have deployed a webpy app using nginx. I run ONE instance of > > webpy but I see 6 threads in htop. I think this come from flups > > someone can explain me how reduce this threads please? > > 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.
