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 serhiy.storchaka
Recipients pitrou, rhettinger, serhiy.storchaka
Date 2013-10-23.19:46:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1382557562.03.0.635238636735.issue19332@psf.upfronthosting.co.za>
In-reply-to
Content
In the first patch the counter was placed in the _dictkeysobject structure. In the second place it is placed in the PyDictObject so it now has no memory cost. Access time to new counter for non-modifying operations is same as in current code. The only additional cost is time cost for modifying operations. But modifying operations is usually much rare than non-modifying operations, and the incrementing one field takes only small part of the time needed for all operation. I don't think this will affect total performance of real programs.
History
Date User Action Args
2013-10-23 19:46:02serhiy.storchakasetrecipients: + serhiy.storchaka, rhettinger, pitrou
2013-10-23 19:46:02serhiy.storchakasetmessageid: <1382557562.03.0.635238636735.issue19332@psf.upfronthosting.co.za>
2013-10-23 19:46:02serhiy.storchakalinkissue19332 messages
2013-10-23 19:46:01serhiy.storchakacreate