[Python-Dev] PEP for new dictionary implementation (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Fri Feb 17 14:34:20 CET 2012
- Previous message: [Python-Dev] PEP for new dictionary implementation
- Next message: [Python-Dev] ctypes/utils.py problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, 17 Feb 2012 13:10:51 +0000 Mark Shannon <mark at hotpy.org> wrote:
On 16/02/12 20:45, Antoine Pitrou wrote: > > On Wed, 08 Feb 2012 19🔞14 +0000 > Mark Shannon<mark at hotpy.org> wrote: >> Proposed PEP for new dictionary implementation, PEP 410? >> is attached. >> > > So, I'm running a few benchmarks using Twisted's test suite > (see https://bitbucket.org/pitrou/t3k/wiki/Home). > > At the end of
python -i bin/trial twisted.internet.test
: > -> vanilla 3.3: RSS = 94 MB > -> new dict: RSS = 91 MB > > At the end ofpython -i bin/trial twisted.python.test
: > -> vanilla 3.3: RSS = 31.5 MB > -> new dict: RSS = 30 MB > > At the end ofpython -i bin/trial twisted.conch.test
: > -> vanilla 3.3: RSS = 68 MB > -> new dict: RSS = 42 MB (!) > > At the end ofpython -i bin/trial twisted.trial.test
: > -> vanilla 3.3: RSS = 32 MB > -> new dict: RSS = 30 MB > > At the end ofpython -i bin/trial twisted.test
: > -> vanilla 3.3: RSS = 62 MB > -> new dict: RSS = 78 MB (!)In theory, new-dict should never use more a few kbs more than vanilla. That looks like a serious leak. I'll investigate as soon as I get a chance. Which revision of new-dict are you using?
6c4d5d9dfc6d
Thanks :)
Antoine.
- Previous message: [Python-Dev] PEP for new dictionary implementation
- Next message: [Python-Dev] ctypes/utils.py problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]