+972 52-548-6969
When you forget to turn off the benchmark when you leave the office…
time to read 1 min | 150 words
On our Slack channel, I just got this:
This is testing high write load on slow I/O device (a network drive).
We didn’t actually forget to turn off the benchmark when we left the office, this is part of our longevity / performance test suite, but it makes for a much better post title, I think you’ll agree.
By the way, this translate to over 16K writes per second sustained for hours on end. And this is testing our behavior on a network drive, because that is the only drive we had off hand with enough capacity for running such a test for long enough.
And then we just left it under load way over the weekend:
Comments
What were you benchmarking? Just network I/O?
Victor, We are looking at overall performance, network cost, I/O costs, resource utilization over time, response rates, etc.
So, more than uint.MaxValue documents in a weekend, poor disk, I think it deserves a vacation now. ;-)
Remco, We routinely abused our disks to the point of wearing them out. Constantly doing db level benchmark work can put a LOT of pressure on a disk
Comment preview