explain.depesz.com

PostgreSQL's explain analyze made readable

Result: eNXw : latancies_analytics

Settings

Optimization(s) for this plan:

# exclusive inclusive rows x rows loops node
1. 0.508 456.064 ↑ 1.0 1,000 1

Limit (cost=0.01..247.46 rows=1,000 width=656) (actual time=38.006..456.064 rows=1,000 loops=1)

  • Buffers: shared hit=191 read=97
  • I/O Timings: read=422.323
2. 27.092 455.556 ↑ 4,990.2 1,000 1

Nested Loop (cost=0.01..1,234,872.60 rows=4,990,200 width=656) (actual time=38.003..455.556 rows=1,000 loops=1)

  • Buffers: shared hit=191 read=97
  • I/O Timings: read=422.323
3. 0.263 370.779 ↑ 71.8 695 1

Append (cost=0.00..49,700.10 rows=49,902 width=80) (actual time=37.892..370.779 rows=695 loops=1)

  • Buffers: shared hit=27 read=90
  • I/O Timings: read=369.328
4. 0.022 0.022 ↓ 0.0 0 1

Seq Scan on latencies (cost=0.00..0.00 rows=1 width=80) (actual time=0.021..0.022 rows=0 loops=1)

  • Filter: ((endtime >= 1549178971) AND (endtime <= 1549265371))
5. 370.494 370.494 ↑ 41.6 695 1

Index Scan using route_latencies_1549144800_endtime_idx on latencies_1549144800 (cost=0.43..28,642.81 rows=28,904 width=80) (actual time=37.868..370.494 rows=695 loops=1)

  • Index Cond: ((endtime >= 1549178971) AND (endtime <= 1549265371))
  • Buffers: shared hit=27 read=90
  • I/O Timings: read=369.328
6. 0.000 0.000 ↓ 0.0 0

Index Scan using route_latencies_1549231200_endtime_idx on latencies_1549231200 (cost=0.43..20,807.77 rows=20,997 width=80) (never executed)

  • Index Cond: ((endtime >= 1549178971) AND (endtime <= 1549265371))
7. 57.685 57.685 ↑ 100.0 1 695

Function Scan on jsonb_each esme (cost=0.01..1.00 rows=100 width=64) (actual time=0.082..0.083 rows=1 loops=695)

  • Buffers: shared hit=32 read=7
  • I/O Timings: read=52.995