I had a 'Lead Programming Manager' once tell me that he'd "benchmarked some RPC code I wrote and it was giving him unacceptable response times" -- thirty seconds between the time he pressed the enter key and the time the browser got updated. After some investigation, I found the bug. It seems that there was a small error with his lap-top's DNS configuration. The first two DNS-servers in his authoritative list were non-existent, due to transposition errors, and the DNS time-out was set to 15 seconds. Once we fixed that, the response time he measured was sub-second. An actual benchmark gave 0.2 seconds from start to finish. (That was about his reaction time, pushing the start/stop timer button on his wrist-watch....)
When you start saying things about program timings, you have to be sure that you are really measuring the code's performance and not side-effects of the other things on the Machine.
----
I Go Back to Sleep, Now.
OGB
In reply to Re: why filling Hash seems slower on unixes than windows ?
by Old_Gray_Bear
in thread why filling Hash seems slower on unixes than windows ?
by vmpilgrim
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |