Plan distribution over time graph docs#23103
Open
bsanchez-the-roach wants to merge 3 commits intomainfrom
Open
Plan distribution over time graph docs#23103bsanchez-the-roach wants to merge 3 commits intomainfrom
bsanchez-the-roach wants to merge 3 commits intomainfrom
Conversation
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
|
✅ Cross-Version Link Check Passed All cross-version link issues have been resolved. Good job! |
Files changed:
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
||
| <img src="{{ 'images/v26.2/ui_plan_table.png' | relative_url }}" alt="Plan table" style="border:1px solid #eee;max-width:100%" /> | ||
|
|
||
| #### Plan Distribution Over Time |
Contributor
Author
There was a problem hiding this comment.
Please verify that the versions that will receive this change {24.3, 25.2, 25.3, 25.4, 26.1, 26.2} are correct.
There was a problem hiding this comment.
@jasonlmfong, can you confirm here please?
Member
There was a problem hiding this comment.
This was not backported so it is only available on 26.2 onwards
|
|
||
| #### Plan Distribution Over Time | ||
|
|
||
| The **Plan Distribution Over Time** graph displays the execution counts for every query plan used within the selected time interval. Each bar in the graph displays the total statement execution count for a given fifteen minute window within the selected interval. If multiple query plans were used in that window, the bar will be stacked, and each query plan will be represented by a different color. The key below the graph indicates the plan gist associated with each color. More information about these query plans can be found in the [plan table](#plan-table). |
Contributor
Author
There was a problem hiding this comment.
This detail here: "for a given fifteen minute window", I don't know that it's correct. Can someone tell me what determines the interval of time by which statement executions are grouped together into a single bar on the graph?
There was a problem hiding this comment.
It should be an hour by default based on the cluster setting. We shouldn't have don't anything differently on the UI for this graph and others. @jasonlmfong, please correct me here.
There was a problem hiding this comment.
Not sure why you saw 15 minutes...perhaps it was the in-memory stats? 🤔 @jasonlmfong
Member
There was a problem hiding this comment.
they are grouped into aggregated timestamps which are by default rounded down to the closest hour
these are able to be affected by the cluster setting sql.stats.aggregation.interval, which affects all things related to statement/transactions stats, which might be why yours was showing 15 minutes?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DOC-15932
Seems like an innocuous ticket but it required a bunch of changes to existing screenshots, and is being backported to older versions, hence all the file changes.
Please verify that the versions here {24.3, 25.2, 25.3, 25.4, 26.1, 26.2} are correct.
Changes to the troubleshooting-query-plan-regressions.md file are only for {25.4, 26.1, 26.2} because older versions don't have that page.