[issue4565] io write() performance very slow

Antoine Pitrou pit...@free.fr added the comment: We can't solve this for 3.0.1, downgrading to critical. -- priority: release blocker - critical ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4565

[issue4565] io write() performance very slow

Changes by Martin v. Löwis mar...@v.loewis.de: -- priority: deferred blocker - release blocker ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4565 ___

[issue4565] io write() performance very slow

Changes by Martin v. Löwis [EMAIL PROTECTED]: -- priority: release blocker - deferred blocker ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue4565 ___

[issue4565] io write() performance very slow

Changes by Winfried Plappert [EMAIL PROTECTED]: -- nosy: +wplappert ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue4565 ___ ___ Python-bugs-list mailing

[issue4565] io write() performance very slow

New submission from Istvan Albert [EMAIL PROTECTED]: The write performance into text files is substantially slower (5x-8x) than that of python 2.5. This makes python 3.0 unsuited to any application that needs to write larger amounts of data. test code follows ---

[issue4565] io write() performance very slow

Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: This is expected: the I/O stack has been completely rewritten... in almost pure-python code. There is a project to rewrite it in C. It started at http://svn.python.org/view/sandbox/trunk/io-c/ -- assignee: - amaury.forgeotdarc

[issue4565] io write() performance very slow

Istvan Albert [EMAIL PROTECTED] added the comment: Well I would strongly dispute that anyone other than the developers expected this. The release documentation states: The net result of the 3.0 generalizations is that Python 3.0 runs the pystone benchmark around 10% slower than Python 2.5.

[issue4565] io write() performance very slow

Changes by Giampaolo Rodola' [EMAIL PROTECTED]: -- nosy: +giampaolo.rodola ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue4565 ___ ___ Python-bugs-list

[issue4565] io write() performance very slow

Antoine Pitrou [EMAIL PROTECTED] added the comment: Hi Amaury, There is a project to rewrite it in C Thanks for publicizing this. I'm a bit surprised by the adopted approach. It seems you are merely translating the Python code into C. I think the proper approach for the buffered IO classes

[issue4565] io write() performance very slow

Christian Heimes [EMAIL PROTECTED] added the comment: For more bug reports see #4533 and #4561. I suggest we close this bug report as duplicate and keep the discussion in #4561. -- nosy: +christian.heimes ___ Python tracker [EMAIL PROTECTED]

[issue4565] io write() performance very slow

Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: I'm a bit surprised by the adopted approach. It seems you are merely translating the Python code into C. I think the proper approach for the buffered IO classes would be to use a fixed-size buffer which never gets reallocated. You

[issue4565] io write() performance very slow

Changes by Barry A. Warsaw [EMAIL PROTECTED]: -- priority: high - release blocker ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue4565 ___ ___