2010/4/21 jazg <[email protected]>: > > Why would it prevent future requests if each request is a new thread? > > I could manually create another thread for the job, but it seems like that > should not be necessary. I still don't understand why setting content-length > didn't work, did pylons decide to override that for some reason?
CherryPy definitely (and AFAIK paster too) uses a pool of worker threads. Starting a new thread for each request would be inefficient (both by having too many concurrent threads and by starting a new thread for each request, which is costly). This is similar to how Apache/mpm_prefork keeps a pool of processes. So, with a pool of eg 10 threads (default for CherryPy) ten requests that start those long-running tasks would deplete the pool completely. Further requests would be queued until one of the workers finishes. -- Paweł Stradomski -- 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.
