-
Notifications
You must be signed in to change notification settings - Fork 231
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
UtilityAnalyzer: EnableConcurrentExecution #6674
Labels
Area: C#
C# rules related issues.
Area: VB.NET
VB.NET rules related issues.
Type: Performance
It takes too long.
Comments
martin-strecker-sonarsource
added
Area: VB.NET
VB.NET rules related issues.
Area: C#
C# rules related issues.
Type: Performance
It takes too long.
labels
Jan 25, 2023
As part of this card, we need to measure the impact before merging it. |
4 tasks
csaba-sagi-sonarsource
assigned csaba-sagi-sonarsource and unassigned martin-strecker-sonarsource and csaba-sagi-sonarsource
May 19, 2023
github-actions
bot
assigned costin-zaharia-sonarsource and unassigned csaba-sagi-sonarsource
May 22, 2023
costin-zaharia-sonarsource
assigned csaba-sagi-sonarsource and unassigned costin-zaharia-sonarsource
May 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area: C#
C# rules related issues.
Area: VB.NET
VB.NET rules related issues.
Type: Performance
It takes too long.
We should EnableConcurrentExecution for the UtilityAnalyzer. See also
#6576 (comment)
Reasoning:
The file writes are protected by a lock already and the collection of the messages can be easily made thread-safe by using a concurrent stack instead of the list. The UtilityAnalyzer contribute a lot to the overall performance and running them concurrently next to the others should help with overall throughput.
Blocked by #6576
The text was updated successfully, but these errors were encountered: