> As for the argument that an application with cpu intensive work being > driven by the IO itself will work itself out... No it won't, it can > get into beat patterns where it is handling requests quite rapidly up > until one that causes a long computation to start comes in. At that > point it'll stop performing well on other requests for as long (it > could be a significant amount of time) as the cpu intensive request > threads are running. That is not a graceful degration in serving > capacity / latency as one would normally expect. It is a sudden drop > off.
Why do you say that? The other threads continue to be served - and Python couldn't use more than one CPU, anyway. Can you demonstrate that in an example? Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
