[Python-Dev] "Fixing" the new GIL

["Martin v. Löwis"]

> 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.
There is nothing to prevent that, unless you schedule the long-running
activity at a point in time where you know the system will be idle for
the entire run of that task.

Regards,
Martin