Thanks Salathe; I know that took awhile to confirm and all. I really appreciate your help.
I'm not sure my math is completely wrong though.
Quote:
|
If the optional get_as_float is set to TRUE then a float (in seconds) is returned.
|
Since
microtime() returns the number of seconds the division into 1,000 is wrong. Thus,
(1 / fSpeed) will give the speed in MB/Sec which can then be divided by 1024.
Here's the problem:
My first version hashes once, yes, but the minimum time it takes to do the whole series is 0.2 seconds! This means I should see a minimum somewhere of either 1.2 or 0.6 in my new tests. I don't. The minimum is ~4.6 seconds and the max is ~5.5; the average should be a little obvious. The max I get with the old is 1 second, hinting to a maximum range of 2-3 seconds for the new.
Before I made a few edits, I don't remember them (like I already said), my new script gave almost EXACTLY the same data and throughput that the old did. Loading time was only twice the old. Then, one save later, the time truly went into the tank. Turning from a 100% increase to almost 700% worth of increase!
Worse the throughput is in the tank too, which it shouldn't be. For one thing, the old lists gost as having a throughput of 130GB/sec while the new says: 0.02 GB/Sec.
There's a HUGE problem here somewhere, and I can't find it to save my life!
Salathe, can you confirm that on your system that the throughputs of the hashes are near identical? I'm not really worried about the time it takes beyond the fact it is a sign of the throughput drop, typically.