Understanding the Query Execution in YugabyteDB

on YouTube ↗26m

" summary

Yugabyte uses the Postgres query layer pluggable into a custom DocDB on RocksDB storage engine, and the planner/executor/optimizer are extended to be shard- and node-aware. Primary vs secondary indexes and hash vs range sharding determine physical ordering; a simple Docker demo compares two tables with different primary keys and shows the same query taking about 5 ms versus 1.7 ms, illustrating a ~3 ms penalty when the index choice forces scanning many rows.

AI-written summary · about

" chapters (10)

1. 0:00YugabyteDB overview
2. 2:02YugabyteDB architecture
3. 4:15PostgreSQL compatibility
4. 7:10Query layer enhancements
5. 9:00Supported PostgreSQL features
6. 10:54Storage layer execution
7. 11:38Key-value storage model
8. 13:28Data sharding impact
9. 17:44Demo: Query performance
10. 24:16Key takeaways

" related talks

• 02h 27mDistributed SQL Tuning and Optimization in YugabyteDBFranck Pachot · Distributed SQL Summit 2022
• 01h 27mYugabyteDB YSQL DevelopmentSeth Luersen · Distributed SQL Summit 2022
• 30mTechnical Comparison of YugabyteDB with Oracle and PostgreSQLFranck Pachot · Distributed SQL Summit Asia 2024
• 27mIntroduction to YugabyteDB: Design and ArchitectureKarthik Ranganathan · Distributed SQL Summit 2020
• 25mYugabyteDB Technical OverviewTOMOHIRO ICHIMURA · Distributed SQL Summit Asia 2022
• 01h 13mExtending PostgreSQL to Google Spanner architectureKarthik Ranganathan · Hydra 2020
• 47mAnatomy of a Distributed SQL Database - YugabyteDBFranck Pachot · Devoxx France 2022
• 27mIntroduction to YugabyteDB – Design and ArchitectureKarthik Ranganathan · Distributed SQL Summit Asia 2021