Charles-François Natali added the comment:
I somehow doubt that the gain is worth the trouble, vectored disk I/O is not as
interesting as vectored read/writes to a NIC.
Actually, a quick search returned this link:
http://www.mail-archive.com/dev@httpd.apache.org/msg23763.html
Running the
Antoine Pitrou added the comment:
Agreed with Charles-François, it probably won't make a difference in practice.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17655
___
STINNER Victor added the comment:
I get similar Fedora 18 (Linux kernel 3.8.1), ext4 filesystem:
$ rm -f writev.out; sync; sleep 5; ./copy_write
copy+write: 1s576530.
$ rm -f writev.out; sync; sleep 5; ./writev
writev: 1s686619.
I agree to close the issue. At least this issue can be used
Changes by Alex Gaynor alex.gay...@gmail.com:
--
nosy: +alex
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17655
___
___
Python-bugs-list mailing
New submission from STINNER Victor:
Since issue #12268 has been fixed, it looks like it became easier to modify the
io to use the writev() function when available.
For example, if FileIO.writelines() uses writev(), it can be used by
TextIOWrapper.write() through BufferedWriter. The
STINNER Victor added the comment:
http://mail.python.org/pipermail/python-dev/2012-August/121396.html
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17655
___
Changes by STINNER Victor victor.stin...@gmail.com:
--
Removed message: http://bugs.python.org/msg186260
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17655
___
STINNER Victor added the comment:
Read also http://mail.python.org/pipermail/python-dev/2012-August/121396.html
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17655
___
