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 alexandre.vassalotti
Recipients alexandre.vassalotti, amaury.forgeotdarc, hagen, pitrou
Date 2008-10-07.21:12:42
SpamBayes Score 6.636413e-09
Marked as misclassified No
Message-id <>
The solution is to add a read buffer to Unpickler (Pickler already has a
write buffer, so that why it is unaffected). I believe this would
mitigate much of the (quite large) Python function call overhead.

cPickle has a performance hack to make it uses cStringIO and PyFile 
directly (via C function calls). In Python 3, the hack was removed since
cStringIO.h and fileobject.h aren't public anymore. This explains the
0.02s deviation you are getting for dump speed.
Date User Action Args
2008-10-07 21:12:44alexandre.vassalottisetrecipients: + alexandre.vassalotti, amaury.forgeotdarc, pitrou, hagen
2008-10-07 21:12:44alexandre.vassalottisetmessageid: <>
2008-10-07 21:12:43alexandre.vassalottilinkissue3873 messages
2008-10-07 21:12:42alexandre.vassalotticreate