➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients Daniel Colascione, amaury.forgeotdarc, belopolsky, davin, meador.inge, pitrou, rhettinger
Date 2017-10-01.17:19:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1506878388.13.0.213398074469.issue31654@psf.upfronthosting.co.za>
In-reply-to
Content 
> Compare-and-exchange is sufficient for avoiding the GIL contention
> I describe above.

If Python objects are involved, it is more complicated than you suggest.  Possibly, multiprocessing can offer a shared counter that creates integer objects on demand and that offers guaranteed atomic increments and decrements (as semaphores) do.

> one of the nice things about multiprocessing is avoiding 
> GIL-introduced latency!

The primary way it achieves this benefit is by avoiding shared state altogether.
History
Date User Action Args
2017-10-01 17:19:48rhettingersetrecipients: + rhettinger, amaury.forgeotdarc, belopolsky, pitrou, meador.inge, davin, Daniel Colascione
2017-10-01 17:19:48rhettingersetmessageid: <1506878388.13.0.213398074469.issue31654@psf.upfronthosting.co.za>
2017-10-01 17:19:48rhettingerlinkissue31654 messages
2017-10-01 17:19:48rhettingercreate