Low-Latency Data Access: The Required Synergy Between Memory & Disk
ScyllaDB
203 views
21 slides
Jun 26, 2024
Slide 1 of 21
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
About This Presentation
Analytics has moved from internal dashboards to a dashboard inside the product, providing a personalized experience for each user, be it the LinkedIn profile views or Uber’s online order management and inventory. Given the requirement of sub-millisecond response times on user-facing apps, how does...
Analytics has moved from internal dashboards to a dashboard inside the product, providing a personalized experience for each user, be it the LinkedIn profile views or Uber’s online order management and inventory. Given the requirement of sub-millisecond response times on user-facing apps, how does one ensure fast analytics on large volumes of data?
There are two main pieces when it comes to data, be it for analytics or transactions – the memory and the disk. Memory or RAM enables fast access to data during active processing, while disk storage offers a much larger storage capacity compared to memory. Both memory and disk are critical components of data processing, each serving different purposes in managing and manipulating data effectively.
In this talk, I will discuss the synergy required between memory and disk to achieve efficient data processing. I will establish a mental model to reason about data organization in memory and disk, for various data access patterns. Further, I will discuss general techniques that databases use for efficient storage and retrieval of data.
Size: 6 MB
Language: en
Added: Jun 26, 2024
Slides: 21 pages
Slide Content
Low-Latency Data Access: The Required Synergy Between CPU, Memory & Disk Kriti Kathuria Database Researcher
Kriti Kathuria ( she/her) Database Researcher Conceptualizing Eventual Durability SQL-gen for Incremental View Maintenance Data Engineer in a past life Good mentorship is powerful and fundamental At scale, the insignificant become significant! ‹#›
Motivation At scale, the insignificant becomes significant! A single IO takes insignificant time But when it is GBs of data and thousands of IO ops, the latencies become significant. Thus, p99, at scale, matters. ‹#›