Run #11
trips · submitted 11 Oct 2026, 18:57
| Row | trip_id | pickup_hour | passengers | distance | price | tip | payment | region | date |
|---|---|---|---|---|---|---|---|---|---|
| 1 | 0 | 12 | 1 | 37.91 | 118.52 | 18.03 | card | EU | 2024-01-01 |
| 2 | 1 | 13 | 1 | 16.11 | 40.46 | NULL | wallet | EU | 2024-01-01 |
| 3 | 2 | 1 | 2 | 24.9 | 75.67 | NULL | wallet | EU | 2024-01-01 |
| 4 | 3 | 8 | 4 | 4.09 | 11.78 | 1.83 | cash | EU | 2024-01-01 |
| 5 | 4 | 16 | 2 | 3.67 | 16.8 | NULL | wallet | EU | 2024-01-01 |
| 6 | 5 | 15 | 4 | 13.14 | 53.96 | 15.23 | cash | EU | 2024-01-01 |
| 7 | 6 | 12 | 2 | 3.21 | 14.37 | NULL | wallet | EU | 2024-01-01 |
| 8 | 7 | 9 | 3 | 17.6 | 44.71 | 7.3 | card | EU | 2024-01-01 |
| 9 | 8 | 15 | 3 | 19.16 | 42.61 | 6.02 | card | EU | 2024-01-01 |
| 10 | 9 | 11 | 3 | 4.0 | 12.14 | NULL | wallet | EU | 2024-01-01 |
| 11 | 10 | 18 | 1 | 14.68 | 46.36 | NULL | wallet | EU | 2024-01-01 |
| 12 | 11 | 6 | 1 | 36.93 | 133.92 | 34.7 | cash | EU | 2024-01-01 |
| 13 | 12 | 16 | 1 | 0.45 | 5.62 | NULL | wallet | EU | 2024-01-01 |
| 14 | 13 | 4 | 2 | 26.8 | 73.73 | 11.26 | cash | EU | 2024-01-01 |
| 15 | 14 | 9 | 1 | 6.96 | 26.41 | 0.33 | card | EU | 2024-01-01 |
| 16 | 15 | 4 | 4 | 31.36 | 108.73 | 16.81 | cash | EU | 2024-01-01 |
| 17 | 16 | 3 | 1 | 7.15 | 34.99 | 10.46 | card | EU | 2024-01-01 |
| 18 | 17 | 19 | 3 | 21.91 | 75.56 | 13.77 | card | EU | 2024-01-01 |
| 19 | 18 | 8 | 1 | 1.02 | 8.45 | 1.45 | card | EU | 2024-01-01 |
| 20 | 19 | 17 | 3 | 30.62 | 99.01 | NULL | cash | EU | 2024-01-01 |
The plan after optimization, which is what actually executed — projection and predicate pushdown have already been applied, so the Scan node shows the columns and filters it really used.
Text plan
Limit 20 Scan trips cols=[*]
Where the bytes went
The middle bars are bytes a scan-everything engine would have read and this one did not. They add up to the full scan exactly — it is one number decomposed, not four separate measurements.
Row-group map (120 of 120 read)
Scan metrics as recorded by the engine
- total_files
- 15
- files_scanned
- 15
- files_pruned
- 0
- total_row_groups
- 120
- row_groups_scanned
- 120
- row_groups_pruned
- 0
- rows_scanned
- 300000
- columns_projected
- 7
- columns_total
- 7
- bytes_scanned
- 6190367
- bytes_total
- 6190367
- bytes_pruned_files
- 0
- bytes_pruned_row_groups
- 0
- bytes_unprojected
- 0
Byte counts are compressed on-disk bytes on both sides of the ratio.
bytes_total covers every row-group including the pruned ones, plus the
file size of files that were never opened.
- Nothing was pruned: this query had no filter the engine could push down, so every file, row-group and column had to be read. This is the baseline the other demo queries are measured against.
The middle bars are bytes a scan-everything engine would have read and this one did not. They add up to the full scan exactly — it is one number decomposed, not four separate measurements.