Message74487
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:44 | alexandre.vassalotti | set | recipients:
+ alexandre.vassalotti, amaury.forgeotdarc, pitrou, hagen |
2008-10-07 21:12:44 | alexandre.vassalotti | set | messageid: <1223413964.64.0.936201901491.issue3873@psf.upfronthosting.co.za> |
2008-10-07 21:12:43 | alexandre.vassalotti | link | issue3873 messages |
2008-10-07 21:12:42 | alexandre.vassalotti | create | |
|