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 vstinner
Recipients alex, gregory.p.smith, neologix, pitrou, vstinner
Date 2013-04-08.19:47:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365450449.78.0.577764282148.issue17655@psf.upfronthosting.co.za>
In-reply-to
Content
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 later is someone else ask why Python is not using writev() ;-)
History
Date User Action Args
2013-04-08 19:47:29vstinnersetrecipients: + vstinner, gregory.p.smith, pitrou, alex, neologix
2013-04-08 19:47:29vstinnersetmessageid: <1365450449.78.0.577764282148.issue17655@psf.upfronthosting.co.za>
2013-04-08 19:47:29vstinnerlinkissue17655 messages
2013-04-08 19:47:29vstinnercreate