Gunicorn used too much memory so I looked for alternatives. I moved webpy to use bjoern + nginx which seemed to speed the pages up especially with 3 concurrent connections (by about 100ms on average better).
The server now lasts about 500,000 requests at 3 concurrent connections before running out of memory. Which leads me to think that the problem lies somewhere in the code i've written. What would be the best way to go about looking for the leak. I tried dozer but I couldn't seem to get it to work. On Jun 14, 2:21 pm, Anand Chitipothu <[email protected]> wrote: > 2011/6/14 Hugh <[email protected]>: > > > > > > > > > > > The main application is started by the following: > > > app=web.application(auth_urls,globals()) > > web.wsgi.runwsgi = lambda func, addr=None: web.wsgi.runfcgi(func, > > addr) > > app.run() > > > runfcgi function is the following (from wsgi.py): > > > def runfcgi(func, addr=('localhost', 8000)): > > import flup.server.fcgi as flups > > return flups.WSGIServer(func, multiplexed=False, > > bindAddress=addr).run() > > > Started the webpy application with the following: > > spawn-fcgi -f /var/www/main.py -a $LOCAL_IP -p $WEB_PORT > > > The guide that I followed to setup webpy and nginx was: > >http://webpy.org/cookbook/fastcgi-nginx > > Flup fastcgi leaks memory. I'm not sure if there is any better fastcgi > library. > > I've been using gunicorn with multiple workers and it has been working > very well for me. But multiple workers many will be too much for an > embedded board. If the #requests/sec is not too high, the you can try > using gunicorn with a single worker. > > http://gunicorn.org/ > > Anand -- 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.
