Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IO times along Execution & planning times along throughput #574

Open
Krysztophe opened this issue Mar 14, 2023 · 1 comment
Open

IO times along Execution & planning times along throughput #574

Krysztophe opened this issue Mar 14, 2023 · 1 comment

Comments

@Krysztophe
Copy link

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
Copy link
Author

Krysztophe commented Mar 14, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant