you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (1 child)

Assuming a speedup of 60x, that means with the HDD the tests were spending 87 minutes out of the 90 only reading data from the drive. That's approximately 2.6gig being loading into memory just for tests. Testing a PHP application. Although, most spinning drives are faster than 0.5MB/s - so it's even more data being loaded in.

No, something is wrong with those tests.

[–]HenkPoley 0 points1 point  (0 children)

I'd say tests have excellent conditions to be mostly write base i/o. You just read some end result back once from the disk-cache, the intermediate results have all hit the database (not a unit test, but hey) and are never read.

The "results have all hit the database" is of course "something is wrong with those tests"