[Python-Dev] Rethinking intern() and its data structure (original) (raw)
John Arbash Meinel john.arbash.meinel at gmail.com
Fri Apr 10 03:24:04 CEST 2009
- Previous message: [Python-Dev] Rethinking intern() and its data structure
- Next message: [Python-Dev] Rethinking intern() and its data structure
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Greg Ewing wrote:
John Arbash Meinel wrote:
And the way intern is currently written, there is a third cost when the item doesn't exist yet, which is another lookup to insert the object. That's even rarer still, since it only happens the first time you load a piece of code that uses a given variable name anywhere in any module.
Somewhat true, though I know it happens 25k times during startup of bzr... And I would be a lot happier if startup time was 100ms instead of 400ms.
John =:->
- Previous message: [Python-Dev] Rethinking intern() and its data structure
- Next message: [Python-Dev] Rethinking intern() and its data structure
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]