Message 186281 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	neologix
Recipients	alex, gregory.p.smith, neologix, pitrou, vstinner
Date	2013-04-08.09:09:05
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1365412145.68.0.678795212657.issue17655@psf.upfronthosting.co.za>
In-reply-to

Content
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 benchmark written by the Apache guys: $ rm -f writev.out; sync; sleep 5; ./test writev: 1s526601. copy+write: 1s323405. Doesn't really surprise me. So I'm -1, since it's unlikely to yield any improvement, and will greatly complicate the code.

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 benchmark written by the Apache guys:
$ rm -f writev.out; sync; sleep 5; ./test
writev: 1s526601.
copy+write: 1s323405.

Doesn't really surprise me.

So I'm -1, since it's unlikely to yield any improvement, and will greatly complicate the code.

History
Date	User	Action	Args
2013-04-08 09:09:05	neologix	set	recipients: + neologix, gregory.p.smith, pitrou, vstinner, alex
2013-04-08 09:09:05	neologix	set	messageid: <1365412145.68.0.678795212657.issue17655@psf.upfronthosting.co.za>
2013-04-08 09:09:05	neologix	link	issue17655 messages
2013-04-08 09:09:05	neologix	create