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 pitrou
Recipients amaury.forgeotdarc, eric.smith, neologix, pitrou
Date 2011-03-03.12:42:22
SpamBayes Score 1.4253706e-08
Marked as misclassified No
Message-id <1299156139.3773.0.camel@localhost.localdomain>
In-reply-to <1299155952.16.0.16875675738.issue11382@psf.upfronthosting.co.za>
Content
> Well, those are contrived examples showing the effect of the convoy
> effect induced by those unneeded GIL release/acquire: releasing and
> re-acquiring the GIL comes with a cost (e.g. under Linux, futex are
> really fast in the uncontended case since handled in use space but
> much slower when there's contention), and subverts the OS scheduling
> policy (forcing the thread to drop/re-acquire the GIL make the thread
> block after having consumed a small amount of its time slice and
> increases the context switching rate). I think that releasing and
> re-acquiring the GIL should only be done around potentially blocking
> calls.

Do you want to propose a patch?
History
Date User Action Args
2011-03-03 12:42:24pitrousetrecipients: + pitrou, amaury.forgeotdarc, eric.smith, neologix
2011-03-03 12:42:22pitroulinkissue11382 messages
2011-03-03 12:42:22pitroucreate