On 12/12/2009 9:31 AM, Preston Landers wrote:
But I'm a little curious about the purpose of having a WSGI thread pool implementation in light of those facts. If ISAPI will create threads for you anyway, how does a pool help? Is it purely to avoid thread startup overhead? If a thread is being created anyway, you're just adding it to a queue to be handled by a separate thread from the pool. Seems like more overhead, not less. But I'm probably missing something there. Nor have I done a hands on performance test.
That is a very good question :) As you have probably noticed, the thread-pool is taking advantage of the async request options provided by ISAPI - so why that functionality exists in the first place seems the same basic question.
I haven't done any measurements on this either - the ISAPI support came with the basic thread-pool implementation when it was contributed. I'd be very interested to know the results of any measurements anyone makes...
Cheers, Mark _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
