dalibo / pev2

Postgres Explain Visualizer 2
https://explain.dalibo.com
PostgreSQL License
2.55k stars 124 forks source link

IO times along Execution & planning times along throughput #574

Closed Krysztophe closed 2 weeks ago

Krysztophe commented 1 year ago

I think that the time spent in IO times should be put as s or ms next to Execution time and Planning Time, instead (of the throughput. image

Examples: https://explain.dalibo.com/plan/dd68b1ag616e05h6#plan and https://explain.dalibo.com/plan/fbdh9341hfb81897#plan : the plans are the same, the time is different, the IO throughput is different, but I don't know immediately if this IO time is a big part of the query or not. The IO time gives a clue about the cache effect. In these plans, you just have to go to the worst node to have the IO time, or to the left pane, but it would tedious in a more complicated plan.

(Throughput is nice though, just less important than absolute time. Of course i'd love to see both at once.)

Krysztophe commented 1 year ago

Another plan with many partitions for testing: https://explain.dalibo.com/plan/5b5024a2egd9bf4c#plan

pgiraud commented 2 weeks ago

What do you think about that: Screenshot from 2024-08-21 14-17-10 Screenshot from 2024-08-21 14-18-36

Should the throughput (average speed) be displayed permanently or in a tooltip on hover to save some space?

Krysztophe commented 2 weeks ago

Nice!

There is enough place for now, so I think you can let the speed as it is.