3 ms·
Persistent Disk read latency is usually good, but jitters up to 100ms. The scheduler can compensate for high latency (essentially applying Little's Law) but can
by seastarer 4y ago
Persistent Disk read latency is usually good, but jitters up to 100ms. The scheduler can compensate for high latency (essentially applying Little's Law) but cannot compensate for jitter without saturating the disk.
- ec109685 4y agoThanks. Do you see the same spikes with ebs volumes on AWS?
- seastarer 4y agoNo.
- deleted 4y ago[deleted]
- seastarer 4y agoSome more data on Google PD: https://raw.githubusercontent.com/scylladb/diskplorer/master/latency-matrix-results/gcp-pd-SSD-2TB.png https://raw.githubusercontent.com/scylladb/diskplorer/master... Very odd - notice how the latency is high when the read IOPS are low. When the read IOPS climb, 95th percentile latency drops. Looks like there is a constant rate of high latency requests, and when the read IOPS climb, that constant rate moves to a higher quantile. I'd inspect the raw results but they're quite big: https://github.com/scylladb/diskplorer/blob/master/latency-matrix-results/gcp-pd-SSD-2TB.json https://github.com/scylladb/diskplorer/blob/master/latency-m... Background: https://github.com/scylladb/diskplorer/ https://github.com/scylladb/diskplorer/
- ec109685 4y agoVery interesting. I wonder if higher iops involves reading from more servers and with request hedging it can smooth latency a lot better.