2010/10/13 Matt Haggard <[email protected]>: > Using flup's fastcgi server, it seems like most threads never die. > > I have a simple app that prints threading.activeCount(), then I use > ab -n 500 -c 20 > to pound it. > > Occasionally, the number of active threads goes down, but it mostly > just goes up and up. Also, memory usage (as monitored in top) > continues to increase as well. > > How can I make sure that the threads die?
Even I had the same problem. I found that it is due to a memory leak in flup. It leaks threads and sockets. Sometimes the process goes out of file descriptors and die. I recently switched to gunicorn[1] webserver on my production site to avoid that issue and it seems to be working quite well. [1]: http://gunicorn.org/ -- 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.
