Chad wrote: > Howdy.. > > I'm testing a pylons site with apache bench in a relatively aggressive > way.. > > ab -n 1000 -c 10 http://127.0.0.1:5000 > > I'm getting tons of these messages.. > > 10:52:22,125 INFO [paste.httpserver.ThreadPool] kill_hung_threads > status: 10 threads (0 working, 10 idle, 0 starting) ave time N/A, max > time 0.00sec, killed 0 workers > > 10:53:18,383 INFO [paste.httpserver.ThreadPool] kill_hung_threads > status: 10 threads (2 working, 8 idle, 0 starting) ave time 0.75sec, > max time 1.00sec, killed 0 workers > > 10:54:16,084 INFO [paste.httpserver.ThreadPool] kill_hung_threads > status: 10 threads (2 working, 8 idle, 0 starting) ave time 0.59sec, > max time 0.98sec, killed 0 workers > > 10:55:12,742 INFO [paste.httpserver.ThreadPool] kill_hung_threads > status: 10 threads (2 working, 8 idle, 0 starting) ave time 0.74sec, > max time 1.13sec, killed 0 workers > > > Can someone tell me exactly what is going on.. Are these errors? Or is > this normal behavior? If these are errors how can I debug what is > going on..
Those aren't errors. I didn't think INFO level messages would typically get printed, but I admit I haven't thought through the logging levels very clearly. It's possible a parent logger could pick up these httpserver messages. When you get more requests than there are worker threads, the thread pool will try to figure out if it should launch more threads, or cull threads that appear to be wedged. In this case it isn't choosing to do either. Ian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
