-
Notifications
You must be signed in to change notification settings - Fork 125
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
Show heap fetches as percent % #589
Comments
The % of blocks is perhaps more important, but you can't have that. The threshold should be rather low. A rather small proportion is already the sign that you need a VACUUM. I hope to find time to test soon. |
I confirm: a few percent of heap fetches is already a disaster. Examples (in the worst case: old computer, default configuration, not enough RAM, slow HDD) :
|
This helps highlighting heap fetches when there's only a few, which can already have significant impact on performance. See #589
This helps highlighting heap fetches when there's only a few, which can already have significant impact on performance. See #589
Won't fix. This doesn't seem very relevant. Instead a warning is displayed each times there's at least one heap fetch. |
It would be nice to get the percentage of rows that are read from the heap.
https://explain.dalibo.com/plan/da11bg7302g59e03#plan/node/11
Plan comes from https://twitter.com/pgMustard/status/1636800885320712216
Also, the warning level may need some adjustments.
The text was updated successfully, but these errors were encountered: