➜

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 Mark.Shannon
Recipients Mark.Shannon, eric.snow, jeremy.kloth, jkloth, larry, maciej.szulik, nanjekyejoannah, ncoghlan, phsilva, rhettinger, shihai1991, vstinner
Date 2020-03-17.18:35:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1584470107.23.0.696421299059.issue39511@roundup.psfhosted.org>
In-reply-to
Content 
Having two CPUs write to the same cache line is a well known performance problem. There's nothing special about CPython here.

The proper name for it seems to be "cache line ping-pong", but a search for "false sharing" might be more informative.
History
Date User Action Args
2020-03-17 18:35:07Mark.Shannonsetrecipients: + Mark.Shannon, rhettinger, ncoghlan, vstinner, larry, jkloth, phsilva, jeremy.kloth, eric.snow, maciej.szulik, nanjekyejoannah, shihai1991
2020-03-17 18:35:07Mark.Shannonsetmessageid: <1584470107.23.0.696421299059.issue39511@roundup.psfhosted.org>
2020-03-17 18:35:07Mark.Shannonlinkissue39511 messages
2020-03-17 18:35:07Mark.Shannoncreate