2 ms·
I've just tried to benchmark, but I'm not sure how. I tried using dd to measure sequential speed and this was giving pretty good results on Google Cloud: > dd
by jchw 9y ago
I've just tried to benchmark, but I'm not sure how. I tried using dd to measure sequential speed and this was giving pretty good results on Google Cloud:
> dd if=/dev/zero of=/dev/disk/by-id/google-local-ssd-0 bs=8192
> 63356186624 bytes (63 GB, 59 GiB) copied, 36.6496 s, 1.7 GB/s
> dd of=/dev/zero if=/dev/disk/by-id/google-local-ssd-0 bs=8192
> 63356186624 bytes (63 GB, 59 GiB) copied, 17.5434 s, 3.6 GB/s
...But I'm perplexed by why it cuts off at 64 GB.
On Amazon I couldn't figure out how to get decent speeds at all. Comparable to my Google Cloud box, I set up an i3.xlarge, which had 4 CPUs and 1 SSD. While the dd operation was working fine, it slowed down to a paltry 430 MB/s quickly and never recovered. I doubt this is the true sequential performance of the drive, so I gave up.
I would've attempted to do multiple SSD configurations, but those seemed even harder. mdadm-based RAIDs were clearly bottlenecking somewhere other than hardware, because they were slower than writing or reading directly.
tl;dr: It turns out these new-fangled NVMe instance store setups are too complicated for me to understand.
- _msw_ 9y agoYou'll need to apply some SSD specific methodology to correctly characterize their performance. Writing zeros to some SSDs will trigger special logic in their flash translation layer (FTL) that will prevent the writes from hitting the flash media. They simply note in the metadata that you wrote some zeros, and reading them back will also be impossibly quick. This isn't the case only on new-fangled NVMe devices...