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 larry
Recipients Mark.Shannon, eric.snow, jeremy.kloth, jkloth, larry, maciej.szulik, nanjekyejoannah, ncoghlan, phsilva, rhettinger, shihai1991, vstinner
Date 2020-03-17.18:17:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> The problem with having a single immortal `None`, is that it will
> cause data cache thrashing as two different CPUs modify the
> refcount on the shared `None` object.

That's a very reasonable theory. Personally, I find modern CPU architecture bewildering and unpredictable.  So I'd prefer it if somebody tests such performance claims, rather than simply asserting them and having that be the final design.
Date User Action Args
2020-03-17 18:17:23larrysetrecipients: + larry, rhettinger, ncoghlan, vstinner, jkloth, phsilva, jeremy.kloth, Mark.Shannon, eric.snow, maciej.szulik, nanjekyejoannah, shihai1991
2020-03-17 18:17:23larrysetmessageid: <>
2020-03-17 18:17:23larrylinkissue39511 messages
2020-03-17 18:17:23larrycreate