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.

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

Investigate the source of a big perf overhead when using analyzers on big solutions. #10068

Closed
Tracked by #9829
AR-May opened this issue Apr 24, 2024 · 1 comment · Fixed by #10186
Closed
Tracked by #9829
Assignees

Comments

@AR-May
Copy link
Member

AR-May commented Apr 24, 2024

Investigate (and fix if possible) ~10s difference in performance on OC rebuild using analyzers (from #9988).

@AR-May
Copy link
Member Author

AR-May commented Jul 2, 2024

I have created a PR that fixes the perf overhead related to loggers. However, there is still significant difference in perf that we need to investigate.

AR-May added a commit that referenced this issue Jul 31, 2024
Fixes #10068

Context
Currently BuildCheckForwardingLogger does not filter out any of the events, which results in extra perf owerhead.

Changes Made
Made BuildCheckForwardingLogger filter out the events that are not used in BuildCheckConnectorLogger.

Testing
Unit tests & manual runs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants