Martin v. Löwis <mar...@v.loewis.de> wrote: > > If it's lurking behind a filesystem interface or in its daemon mode > > (remote archive store), multiple client processes can be using it at once, > > and it will be processing multiple tasks somewhat in parallel. Here one > > can get a compute bound thread answering one request, impacting quick > > response to other parallel-and-cheap requests. > > However, "impacting" will always be the case. *Of course* any thread > that performs computation impacts everything else on the same processor.
That's not the problem, Martin. The problem is that it also impacts other threads on other cores, because of the interlock between the OS thread scheduler and the internal Pythonic struggle to obtain the GIL. And it shouldn't. Bill _______________________________________________ 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
