Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Boyan Ivanov - latency, the #1 metric of your cloud

341 views

Published on

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.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Boyan Ivanov - latency, the #1 metric of your cloud

  1. 1. Latency: the #1 metric of your cloud CloudStack User Group, 14 Mar 2019
  2. 2. ops/transactionspersecond Dependency of any transaction processing system Latency Databases Web Servers Load balancers Storage systems Etc.
  3. 3. core core core core task Balancing work to be done with system resources
  4. 4. core core core core task task Balancing work to be done with system resources – 50%
  5. 5. core core core core task task task task Balancing work to be done with system resources – 100%
  6. 6. Latency opspersecond increasingload0->100% Elasticity of an “ideal system in vacuum”
  7. 7. Latency opspersecond Elasticity of real systems
  8. 8. core core core core task task task task task task System overload
  9. 9. Latency opspersecond Regimes of any transaction processing system
  10. 10. Latency opspersecond best service
  11. 11. Latency opspersecond best service lowest cost per delivered resource
  12. 12. Latency opspersecond best service lowest cost per delivered resource only pain
  13. 13. Latency opspersecond best service lowest cost per delivered resource only pain systemthroughput
  14. 14. Latency opspersecond best service lowest cost per delivered resource only pain benchmarks
  15. 15. Latency opspersecond 10kIOPS
  16. 16. https://www.digitalocean.com/docs/volumes/
  17. 17. https://www.digitalocean.com/docs/volumes/overview/ Metrics of a Cloud Storage Layer
  18. 18. https://www.digitalocean.com/docs/volumes/overview/ Latency The most important metric is Missing! Where is my Latency?!
  19. 19. 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
  20. 20. 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!
  21. 21. 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
  22. 22. A small experiment
  23. 23. Latency opspersecond 10kIOPS 2ms A volume with 2ms latency…
  24. 24. Latency opspersecond 10kIOPS 0.3ms …Vs. a volume with 0.3ms latency
  25. 25. 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
  26. 26. 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
  27. 27. DEMO (embedded video on next slide) /or click here if video does not play/
  28. 28. Click here if video does not play
  29. 29. 4 vCPUs, 4 GB RAM vdisk with 10k IOPS 2ms storage latency = 900 TPS @ 8 ms pgbench Results – slow volume
  30. 30. 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!
  31. 31. 4 vCPUs, 4 GB RAM vdisk with 10k IOPS 0.3ms storage latency = 1600 TPS @ 5 ms pgbench Results – fast volume
  32. 32. 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
  33. 33. 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?
  34. 34. 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?
  35. 35. Boyan Ivanov StorPool Storage info@storpool.com www.storpool.com @storpool Thank you + Q&A!

×