Boyan Ivanov - latency, the #1 metric of your cloud
•
1 like•671 views
No two clouds are the same. Yet the leading clouds all have one thing in common: they deliver on metrics, which matter to the customer. In this session we'll dissect leading clouds, to show why low latency is the thing that makes a cloud stand out.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Boyan Ivanov - latency, the #1 metric of your cloud
Similar to Boyan Ivanov - latency, the #1 metric of your cloud (20)
More from ShapeBlue
More from ShapeBlue (20)
Recently uploaded
Recently uploaded (20)
Boyan Ivanov - latency, the #1 metric of your cloud
- 1. Latency: the #1 metric of your cloud CloudStack User Group, 14 Mar 2019
- 2. ops/transactionspersecond Dependency of any transaction processing system Latency Databases Web Servers Load balancers Storage systems Etc.
- 3. core core core core task Balancing work to be done with system resources
- 4. core core core core task task Balancing work to be done with system resources – 50%
- 5. core core core core 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. Latency opspersecond Elasticity of real systems
- 8. core core core core task task task task task task System overload
- 9. Latency opspersecond Regimes of any transaction processing system
- 11. Latency opspersecond best service lowest cost per delivered resource
- 12. Latency opspersecond best service lowest cost per delivered resource only pain
- 13. Latency opspersecond best service lowest cost per delivered resource only pain systemthroughput
- 14. Latency opspersecond best service lowest cost per delivered resource only pain benchmarks
- 19. https://www.digitalocean.com/docs/volumes/overview/ Metrics of a Cloud Storage Layer
- 20. https://www.digitalocean.com/docs/volumes/overview/ Latency The most important metric is Missing! Where is my Latency?!
- 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.51 ms 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.51 ms 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
- 25. Latency opspersecond 10kIOPS 2ms A volume with 2ms latency…
- 26. Latency opspersecond 10kIOPS 0.3ms …Vs. a volume with 0.3ms latency
- 27. 4 vCPUs, 4 GB 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, 4 GB 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 on next slide) /or click here if video does not play/
- 30. Click here if video does not play
- 31. 4 vCPUs, 4 GB RAM vdisk with 10k IOPS 2ms storage latency = 900 TPS @ 8 ms pgbench Results – slow volume
- 32. 4 vCPUs, 4 GB 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, 4 GB RAM vdisk with 10k IOPS 0.3ms storage latency = 1600 TPS @ 5 ms pgbench Results – fast volume
- 34. 4 vCPUs, 4 GB 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, 16 GB 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, 16 GB RAM, dedicated if offered, database size = 4x RAM https://wiki.postgresql.org/wiki/Pgbenchtesting Comparing Clouds – who can run a database?