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 nadeem.vawda, neologix, pitrou, ronaldoussoren, santoso.wijaya, sdaoden, vstinner
Date 2011-05-15.20:11:28
SpamBayes Score 1.032665e-07
Marked as misclassified No
Message-id <1305490289.16.0.924530468568.issue11877@psf.upfronthosting.co.za>
In-reply-to
Content
(I'm not sure Rietveld sent the message so I post it here, sorry in case of duplicate).

Steffen, I've made a quick review of your patch, in case you're interested.
I think that this functionality can be really useful to some people, and it'd be
nice if your patch could stabilize somewhat so that committers can review it
properly and eventually merge it.

Concerning your benchmark:
I don't know exactly what you're measuring, but when performing I/O-related
benchmarks, it's always a good idea to run each test several times in a row, or
flush the page/buffer cache before each run: the reason is that the the second
run benefits from the page/buffer cache, which often speeds things up
dramatically.
Example:

# time find /lib -type f -exec cat {} \; > /dev/null 
real    0m20.455s
user    0m8.145s
sys     0m5.256s

# time find /lib -type f -exec cat {} \; > /dev/null 
real    0m6.827s
user    0m8.477s
sys     0m4.804s

# echo 3 > /proc/sys/vm/drop_caches 

# time find /lib -type f -exec cat {} \; > /dev/null 
real    0m19.954s
user    0m8.069s
sys     0m5.364s
History
Date User Action Args
2011-05-15 20:11:29neologixsetrecipients: + neologix, ronaldoussoren, pitrou, vstinner, nadeem.vawda, santoso.wijaya, sdaoden
2011-05-15 20:11:29neologixsetmessageid: <1305490289.16.0.924530468568.issue11877@psf.upfronthosting.co.za>
2011-05-15 20:11:28neologixlinkissue11877 messages
2011-05-15 20:11:28neologixcreate