| Weblog: | The Python comunity has too many deceptive XML benchmarks | |
| Subject: | Wow. | |
| Date: | 2005-01-24 03:22:31 | |
| From: | effbot | |
|
"I ran each case 5 times and recorded the high and low run times, according to the UNIX time command"
|
||
Showing messages 1 through 4 of 4.
-
Wow.
2005-01-25 08:50:46 AaronWatters [Reply | View]
-
Wow.
2005-01-25 15:29:35 effbot [Reply | View]
Benchmarking individual components really isn't a black art. Just make sure you eliminate all irrelevant stuff from the measurements, use the best timing device you have access to, run the tests multiple times, and pick the best observed time (unless the object you're studying involves random elements). Make sure your math and your logic is sound; if A and B are large numbers, A+B doesn't equal max(A, B). If you're measuring really fast things, you need to be more careful. If you want prior art, study available tools (such as timeit). If anything I just said is news to you, don't do benchmarks. No need to be stupid. Being stupid only makes you look like a fool.
-
Wow.
2005-01-25 08:50:46 AaronWatters [Reply | View]
Hmmm... maybe benchmarks of this ilk should go
through some sort of peer review before they are
widely publicized? Just a thought.
| Showing messages 1 through 4 of 4. |
through some sort of peer review before they are
widely publicized? Just a thought.