5 ms·
I've observed exactly this behaviour on TB volumes on AWS instances, is it known if they use this sort of drive?
by jjgreen 7y ago
I've observed exactly this behaviour on TB volumes on AWS instances, is it known if they use this sort of drive?
- gray_-_wolf 7y agoThat is probably more relates to IOPS credits I would think.
- ciceryadam 7y agoCheck I/O Credits and Burst Performance at https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volume-types.html https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volu...
- toolslive 7y agodon't assume that if you hire a volume on AWS that you get a device. The thing you get is a virtual block device and is actually the entry point of a sophisticated piece of software that will spread your data over multiple devices (might be erasure coded, might be replicated, probably hierarchical, so data comes in on NVMe, is then moved to SSD and eventually to HDD). So whatever you're seeing, it's not the behaviour of a single HDD.
- jjgreen 7y agoThanks for all the pointers!