Good catch MK. I had caught that but neglected to update my command here. flow control is on.
Fred, you're providing a great service. Do you feel like your result-set can basically be used as a size benchmark on the Real Life results?
I feel like my limiters are spindle count and spin rate. Even during the max throughput test I can see in the EQL performance data that the network ports are only working at 50%. I guess the iSCSI network ports will start to play a role at the point I have many guests pushing big IO? The EQL has 4 ports for iSCSI while the ESXi hosts have 2. Will that give me some room to upgrade if I hit this limit?
One question about the tests vs. real life: In real life yesterday, the devs copied a 133Gb backup database directory, containing 1x100Gb file and a few others, between the production and dev SQL server. They are on the same host but different LUNs. IO rate was spot on with Max Throughput, 50% read. IOPS were significantly lower - about a third. And I saw an initial read latency spike up to 60 ms, then sustained write latency averaging 24ms with two 5 minute spike to 40ms.
The tests don't seem to trigger the latency but I'm using a quiet host and datastore for testing. Is that the difference there?