Eyal Gutkind, VP of Solutions at ScyllaDB, discusses the importance of managing database latency for user experience, system stability, and liability. He outlines various sources of latency including hardware issues, database architecture, and data modeling, emphasizing the need for proper application sizing and performance tuning. The document calls for collaboration among developers, DevOps, and system operators to effectively control latencies.

1. Keeping your latency
SLAs No Matter What
Eyal Gutkind, VP of Solutions, ScyllaDB

2. Presenter
2
Eyal Gutkind
Eyal Gutkind is VP of Solutions at ScyllaDB leading the
solutions team focused on user experience and
satisfaction with Scylla products. Prior to joining ScyllaDB,
Eyal held product management roles at Mirantis and
DataStax, and spent 12 years with Mellanox Technologies
in various engineering management and product marketing
roles.

3. Why should you care about DB latency?
+ User experience
+ System stability
+ Liability

4. Where do latencies
come from?

5. Hardware has all the faults, Right?!
+ Disk seek time
+ SSD latency
+ Media buffering

6. Hardware has all the faults, Right?!
+ How far are you from your data?
+ Data routing
+ Network technologies

7. Hardware has all the faults, Right?!
+ Compute resources

8. Database Architecture Contribution
+ Primary-Secondary architecture Databases

9. Database Architecture Contribution
+ Primary-Secondary architecture Databases
+ Single threaded Databases

10. Database Architecture Contribution
+ Primary-Secondary architecture Databases
+ Single threaded Databases
+ Virtual Machine dependent Databases

11. What about your data model?
+ Hot partitions
+ Full table scans
+ Reverse ordering of data
+ Cross data center transactions

12. Sizing poll

13. Solved by Scylla

14. C++ instead of Java
14

15. Shard per Core
Threads Shards
15

16. Unified Cache
Cassandra Scylla
Key
cache
Row
cache
Linux page cache
SSTables
Unified cache
SSTables
Complex Tuning
On-heap /
Off-heap
16

17. I/O Scheduler
17

18. Self-Optimizing
18

19. Driver opens connections to all CPUs,
and learns which tokens
belong to each CPU.
Request is sent directly to owner.
CPU that owns
the token
Token
Shard-aware drivers - Scylla

20. How our customers
solved the latency
issues

22. 22
+
+
+

23. Ok, can we have
the recipe?

24. Size your application properly
+ Business needs
+ High Availability
+ Application performance tuning

25. Hardware
+ Select non-blocking building blocks
+ Ample amount of CPU, memory, media and network bandwidth
+ IaaS
+ NVMe based instances
+ On - Prem
+ Focus on media and network bandwidth

26. Data modeling
+ Partition Key entropy
+ Query design
+ Monitoring, Monitoring, Monitoring

27. Summary
+ We can control latencies
+ Developers, DevOps and System operators need to collaborate
+ Database architecture has an impact on your tail-end latencies
+ Low hanging fruits
+ Data modeling
+ Traffic patterns
+ Test drive your application

28. Stay in touch
eyal@scylladb.com
@gutkinde
Q&A

29. United States
2445 Faber St, Suite #200
Palo Alto, CA USA 94303
Israel
Maskit 4
Herzliya, Israel 4673304
www.scylladb.com
@scylladb
Thank You!