-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[Exec](profile) add max row count one backend in materialization profile #59728
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
Merged
+21
−0
Conversation
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
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
Author
|
run buildall |
TPC-H: Total hot run time: 32266 ms |
TPC-DS: Total hot run time: 173255 ms |
Contributor
|
skip check_coverage |
BiteTheDDDDt
approved these changes
Jan 12, 2026
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
yiguolei
approved these changes
Jan 12, 2026
github-actions bot
pushed a commit
that referenced
this pull request
Jan 12, 2026
…ile (#59728) - Add `_backend_rows_count` to `MaterializationSharedState` to count the number of rows assigned to each backend during block distribution. - Introduce `_max_rows_per_backend` to record the maximum row count handled by any single backend in the current batch. - Update `merge_multi_response()` to compute `_max_rows_per_backend` after row assignment. - Expose this metric via a new runtime profile counter `MaxRowsPerBackend` in `MaterializationLocalState`. - This helps monitor data skew across backends and aids in performance debugging for materialization-heavy queries.
yiguolei
pushed a commit
that referenced
this pull request
Jan 13, 2026
…ization profile #59728 (#59758) Cherry-picked from #59728 Co-authored-by: HappenLee <[email protected]>
zzzxl1993
pushed a commit
to zzzxl1993/doris
that referenced
this pull request
Jan 13, 2026
…ile (apache#59728) - Add `_backend_rows_count` to `MaterializationSharedState` to count the number of rows assigned to each backend during block distribution. - Introduce `_max_rows_per_backend` to record the maximum row count handled by any single backend in the current batch. - Update `merge_multi_response()` to compute `_max_rows_per_backend` after row assignment. - Expose this metric via a new runtime profile counter `MaxRowsPerBackend` in `MaterializationLocalState`. - This helps monitor data skew across backends and aids in performance debugging for materialization-heavy queries.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
What problem does this PR solve?
feat(materialization): track and expose max rows per backend metric
_backend_rows_counttoMaterializationSharedStateto count the number of rows assigned to each backend during block distribution._max_rows_per_backendto record the maximum row count handled by any single backend in the current batch.merge_multi_response()to compute_max_rows_per_backendafter row assignment.MaxRowsPerBackendinMaterializationLocalState.Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)