[issue4565] io write() performance very slow

2008-12-20 Thread Antoine Pitrou
Antoine Pitrou added the comment: We can't solve this for 3.0.1, downgrading to critical. -- priority: release blocker -> critical ___ Python tracker ___

[issue4565] io write() performance very slow

2008-12-19 Thread Martin v. Löwis
Changes by Martin v. Löwis : -- priority: deferred blocker -> release blocker ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue4565] io write() performance very slow

2008-12-10 Thread Martin v. Löwis
Changes by Martin v. Löwis <[EMAIL PROTECTED]>: -- priority: release blocker -> deferred blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue4565] io write() performance very slow

2008-12-07 Thread Winfried Plappert
Changes by Winfried Plappert <[EMAIL PROTECTED]>: -- nosy: +wplappert ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list ma

[issue4565] io write() performance very slow

2008-12-06 Thread Barry A. Warsaw
Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: high -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Pyth

[issue4565] io write() performance very slow

2008-12-06 Thread Amaury Forgeot d'Arc
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.

[issue4565] io write() performance very slow

2008-12-06 Thread Christian Heimes
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

2008-12-06 Thread Antoine Pitrou
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

2008-12-06 Thread Giampaolo Rodola'
Changes by Giampaolo Rodola' <[EMAIL PROTECTED]>: -- nosy: +giampaolo.rodola ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-

[issue4565] io write() performance very slow

2008-12-06 Thread Istvan Albert
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

2008-12-06 Thread Amaury Forgeot d'Arc
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.forgeotda

[issue4565] io write() performance very slow

2008-12-06 Thread Istvan Albert
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 --