RetroSearch Browse

Mon Mar 15 09:34:03 CET 2010 · http://mail.python.org/pipermail/python-dev/2010-March/098418.html

> So, just to be clear about the my bug report, it is directly related
> to the problem of overlapping I/O requests with CPU-bound processing.
> This kind of scenario comes up in the context of many
> applications--especially those based on cooperating processes,
> multiprocessing, and message passing.

How so? if you have cooperating processes, multiprocessing, and message
passing, you *don't* have CPU bound threads along with IO "bound"
threads in the same process - you may not have threads at all!!!

> In any case, if the GIL can be improved in a way that is simple and
> which either improves or doesn't negatively impact the performance of
> existing applications, why wouldn't you want to do it?  Seems like a
> no-brainer.

Unfortunately, a simple improvement doesn't really seem to exist.

Regards,
Martin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2010-March/098418.html below:

[Python-Dev] "Fixing" the new GIL