Message 80097 - Python tracker

➜

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	hagen
Recipients	alexandre.vassalotti, amaury.forgeotdarc, hagen, pitrou
Date	2009-01-18.13:40:35
SpamBayes Score	5.988447e-08
Marked as misclassified	No
Message-id	<1232286037.36.0.739031096489.issue3873@psf.upfronthosting.co.za>
In-reply-to

Content
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. Is this expected at this point of io-c development? Otherwise perhaps this issue should stay open until it can be verified that nothing else can be done to get closer to the old cPickle performance.

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.

Is this expected at this point of io-c development? Otherwise perhaps
this issue should stay open until it can be verified that nothing else
can be done to get closer to the old cPickle performance.

History
Date	User	Action	Args
2009-01-18 13:40:37	hagen	set	recipients: + hagen, amaury.forgeotdarc, pitrou, alexandre.vassalotti
2009-01-18 13:40:37	hagen	set	messageid: <1232286037.36.0.739031096489.issue3873@psf.upfronthosting.co.za>
2009-01-18 13:40:36	hagen	link	issue3873 messages
2009-01-18 13:40:35	hagen	create