Add configuration option to permit collection of more execution plans
💪 Now available
Currently DBMarlin appears to limit SQL execution plan collection to only the top 10 statements. Please add an option to collect more (or all!) execution plans
The algorithm will now randomly gather plans for statement outside the top 20 as well. This can be useful if a statement which is normally a low resource consumer outside of the top 20 suddenly changes behaviour and comes into the top 20, you can then see if the plan changed.
Good idea. How far down the list would you need to go? If we set explain top N too high that might become an overhead so probably need some safeguard built-in.
Hi Mick, could there be maybe a feature to also be able to load an execution plan on demand? Besides the bulk load of top N? Like if we investigate a few sql statements related to one User even if they are not in top N we could load execution plan on demand for each instead of checking it in DB.
@Paulavicovan: I also think this would be a good feature. On the fly be able to explain a particular statement, not necesarly keep the plan in DBmarlin
This is now available since DBmarlin v3.12
0 2 months ago Reply
The default was change from top 10 to top 20 and the value can be controlled by the parameter
inexplain_limitwebapps/agent/META-INF/context.xmlhttps://docs.dbmarlin.com/docs/faqs/frequently-asked-questions/#collecting-more-execution-plans
The algorithm will now randomly gather plans for statement outside the top 20 as well. This can be useful if a statement which is normally a low resource consumer outside of the top 20 suddenly changes behaviour and comes into the top 20, you can then see if the plan changed.
0 2 months ago Reply
6 months ago
Good idea. How far down the list would you need to go? If we set explain top N too high that might become an overhead so probably need some safeguard built-in.
0 2 years ago Reply
Hi Mick, could there be maybe a feature to also be able to load an execution plan on demand? Besides the bulk load of top N? Like if we investigate a few sql statements related to one User even if they are not in top N we could load execution plan on demand for each instead of checking it in DB.
0 2 years ago Reply
@Paulavicovan: I also think this would be a good feature. On the fly be able to explain a particular statement, not necesarly keep the plan in DBmarlin
0 1 year ago Reply