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 pitrou
Recipients alexandre.vassalotti, amaury.forgeotdarc, hagen, pitrou
Date 2009-01-18.14:01:19
SpamBayes Score 1.1002774e-05
Marked as misclassified No
Message-id <1232287301.6604.4.camel@localhost>
In-reply-to <1232286037.36.0.739031096489.issue3873@psf.upfronthosting.co.za>
Content
Hello,

> With the io-c branch I see much better unpickling performance than
> before. But it still seems to be around 2 or 3 times slower than with
> cPickle in 2.6.

It's much closer here.

With 2.7 (trunk) and cPickle:
0.439934968948
0.669679880142
With the io-c branch:
0.136367082596
0.798221111298

> Is this expected at this point of io-c development?

20-30% slower is expected for binary I/O (which is what I get above),
not 2x or 3x slower.
What is your system?
History
Date User Action Args
2009-01-18 14:01:20pitrousetrecipients: + pitrou, amaury.forgeotdarc, alexandre.vassalotti, hagen
2009-01-18 14:01:19pitroulinkissue3873 messages
2009-01-18 14:01:19pitroucreate