~/talk

Database Highload: When to Scale and When to Optimize

TalkinRussianat Highload fwdays'19 · on Saturday, 2019-10-05· [databases]
links:none on file
slides:none on file

Shows how to decide between scaling and optimizing using concrete metrics (CPU%, requests/sec, disk latency/IOPS, cache life) rather than buzzwords. Describes capturing queries with extended events into a table (example: highload) to group by text and find hot spots, then profiling a slow stored procedure (transaction_history) that took 69s vs others at 12s and cutting its cost by ~90% through targeted optimization. Also warns that SAN drivers or network latency can introduce random 1–30ms disk I/O spikes that affect performance.

AI-written summary · about

  1. 0:00Introduction
  2. 1:10Why databases slow down
  3. 3:40Scalability markers
  4. 7:30When scaling fails
  5. 10:44Diminishing returns in scaling
  6. 13:18Memory and caching issues
  7. 16:08Disk load and latency
  8. 21:13Cloud vs bare-metal scaling
  9. 24:28Finding load sources
  10. 25:53Query tracing demo
  11. 30:26Query optimization and load balancing
  12. 35:27Scale or optimize decisions
  13. 36:52Optimization vs scaling takeaways
  14. 38:39Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.