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.

Sign up for GitHub

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

Jump to bottom

Improve stats reporting for group by operator #21925

Open
sopel39 opened this issue May 10, 2024 · 2 comments
Open

Improve stats reporting for group by operator #21925

sopel39 opened this issue May 10, 2024 · 2 comments
Assignees
@sug-ghosh
Labels
good first issue Good for newcomers performance

Comments

@sopel39
Copy link
Member

sopel39 commented May 10, 2024 •
edited

Similarly as in f46fd9c we could separately report hash lookups/updates and aggregations' accumulator updates to get more insight into query bottlenecks.

cc @dain @raunaqmorarka
@sug-ghosh
Copy link

I want to take this up, @sopel39 can you give more insight of this.

@sopel39
Copy link
Member Author

sopel39 commented May 24, 2024

I want to take this up, @sopel39 can you give more insight of this.

Sure go ahead. Take a look at commit f46fd9c. You can see that ScanFilterAndProjectOperator keeps projection and fitltering stats in PageProcessorMetrics, which are then returned as operator metrics. Similar approach could be applied for group by operator. We can measure performance of GroupByHash and Accumulator separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sug-ghosh sug-ghosh

Labels
good first issue Good for newcomers performance
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sopel39 @sug-ghosh