[issue1675951] Performance for small reads and fix seek problem
report at bugs.python.org
Wed Sep 22 12:09:30 CEST 2010
Florian Festi <florianfesti at users.sourceforge.net> added the comment:
Stupid me! I ran the tests against my systems gzip version (Py 3.1). The performance issue is basically fixed by rev 77289. Performance is even a bit better that my original patch by may be 10-20%. The only test case where it performs worse is
Random 10485760 byte block test
Original gzip Write: 20.452 s Read: 2.931 s
New gzip Write: 20.518 s Read: 1.247 s
Don't know if it is worth bothering. May be increasing the maximum chunk size improves this - but I didn't try that out yet.
WRT to seeking:
I now have two patches that eliminate the need for seek() on normal operation (rewind obviously still needs seek()). Both are based on the PaddedFile class. The first patch just creates a PaddedFile object while switching from an old to a new member while the second just wraps the fileobj all the time. Performance test show that wrapping is cheap. The first patch is a bit ugly while the second requires a implementation of seek() and may create problems if new methods of the fileobj are used that may interfere with the PaddedFile's internals.
So I leave the choice which one is preferred to the module owner.
The patch creates another problem with is not yet fixed: The implementation of .seekable() is becoming wrong. As one can now use non seekable files the implementation should check if the file object used for reading is really seekable. As this is my first PY3k work I'd prefer if this can be solved by someone else (But that should be pretty easy).
Added file: http://bugs.python.org/file18964/0001-Avoid-the-need-of-seek-ing-on-the-file-read.patch
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list