Download to read offline
Uploaded byShapeBlue
Boyan Ivanov - latency, the #1 metric of your cloud
The document discusses the critical role of latency as a metric in cloud computing, particularly in transaction processing systems. It provides comparisons of latency performance across various cloud providers and storage configurations, highlighting that AWS offers significantly lower latency than others at a higher cost. The document also presents experimental results demonstrating the impact of latency on system throughput and performance in different scenarios.
More Related Content
Similar to Boyan Ivanov - latency, the #1 metric of your cloud
Boyan Ivanov - latency, the #1 metric of your cloud
- 1. Latency: the #1metric of your cloud CloudStack User Group, 14 Mar 2019
- 2. ops/transactionspersecond Dependency of anytransaction processing system Latency Databases Web Servers Load balancers Storage systems Etc.
- 3. core core corecore task Balancing work to be done with system resources
- 4. core core corecore task task Balancing work to be done with system resources – 50%
- 5. core core corecore task task task task Balancing work to be done with system resources – 100%
- 6. Latency opspersecond increasingload0->100% Elasticity of an“ideal system in vacuum”
- 7.
- 8. core core corecore task task task task task task System overload
- 9. Latency opspersecond Regimes of anytransaction processing system
- 10.
- 11. Latency opspersecond best service lowest costper delivered resource
- 12. Latency opspersecond best service lowest costper delivered resource only pain
- 13. Latency opspersecond best service lowest costper delivered resource only pain systemthroughput
- 14. Latency opspersecond best service lowest costper delivered resource only pain benchmarks
- 17.
- 18.
- 19. https://www.digitalocean.com/docs/volumes/overview/ Metrics of aCloud Storage Layer
- 20.
- 21. random read/write 50/50,4k, QD 1 avg. latency DreamHost/DreamCompute (Ceph) 4.51 ms DigitalOcean (Ceph) 1.75 ms OVH (Ceph) 1.53 ms Comparing some public Clouds
- 22. DreamHost/DreamCompute (Ceph) 4.51ms DigitalOcean (Ceph) 1.75 ms OVH (Ceph) 1.53 ms AWS EBS gp2 10k ($333/mo) 0.29 ms Comparing some public Clouds random read/write 50/50, 4k, QD 1 avg. latency 5 to 15 times faster! For a lot of $$$ thought!
- 23. DreamHost/DreamCompute (Ceph) 4.51ms DigitalOcean (Ceph) 1.75 ms OVH (Ceph) 1.53 ms AWS EBS gp2 10k ($333/mo) 0.29 ms eApps ($50/mo) 0.41 ms Togglebox ($20/mo) 0.21 ms StorPool BCP (Best Current Practice) 0.17 ms random read/write 50/50, 4k, QD 1 avg. latency Best-of-breed Clouds
- 24.
- 25. Latency opspersecond 10kIOPS 2ms A volume with2ms latency…
- 26. Latency opspersecond 10kIOPS 0.3ms …Vs. a volumewith 0.3ms latency
- 27. 4 vCPUs, 4GB RAM vdisk with 10k IOPS "fast" volume with approx 0.3 ms latency (QD 1) "slow" volume with 2 ms latency (QD 1) with dm-delay in host Both volumes are on the same SSD pool Both volumes measure 10k IOPS flat Same test VMs in all Cloud providers 2 disks – slow & fast
- 28. 4 vCPUs, 4GB RAM vdisk with 10k IOPS pgbench --client=8 --jobs=4 --progress=1 --time=5 pgbench4x database size: 16 GB (4x RAM) https://wiki.postgresql.org/wiki/Pgbenchtesting Same test
- 29. DEMO (embedded video onnext slide) /or click here if video does not play/
- 30. Click here ifvideo does not play
- 31. 4 vCPUs, 4GB RAM vdisk with 10k IOPS 2ms storage latency = 900 TPS @ 8 ms pgbench Results – slow volume
- 32. 4 vCPUs, 4GB RAM vdisk with 10k IOPS 2ms storage latency = 900 TPS @ 8 ms pgbench -> if we ask for 1200 TPS -> pile up Results – slow volume under pressure – congestion!
- 33. 4 vCPUs, 4GB RAM vdisk with 10k IOPS 0.3ms storage latency = 1600 TPS @ 5 ms pgbench Results – fast volume
- 34. 4 vCPUs, 4GB RAM vdisk with 10k IOPS 0.3ms storage latency = 1600 TPS @ 5 ms pgbench -> if we ask for 1200 TPS - no problem Results – fast volume under pressure – no problem
- 35. 8 vCPUs, 16GB RAM, dedicated if offered, database size = 4x RAM https://wiki.postgresql.org/wiki/Pgbenchtesting Comparing Clouds – AWS seems to rule them all?
- 36. 8 vCPUs, 16GB RAM, dedicated if offered, database size = 4x RAM https://wiki.postgresql.org/wiki/Pgbenchtesting Comparing Clouds – who can run a database?
- 37.