You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.)
The text was updated successfully, but these errors were encountered:
I think that the time spent in IO times should be put as
s
orms
next to Execution time and Planning Time, instead (of the throughput.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.)
The text was updated successfully, but these errors were encountered: