Utility analyzer: Enable concurrent analysis and use producer/consumer pattern for file writes #8459
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.
Fixes #6674
Fixes #8460
Akka test (dotnet build in Sonar context):
The Utility Analyzers in Akka create 936 protobuf files with a total size of 35.195.405 bytes/35MB (ucfgs excluded). 75% of the 35MB are contributed by the CopyPasteTokenAnalyzer (token-cpd.pb).
AnalyzerRunner (Akka)
C:\Projects\OpenSource\roslyn\artifacts\bin\AnalyzerRunner\Release\net7.0\AnalyzerRunner.exe C:\Projects\sonar-dotnet\analyzers\packaging\binaries "C:\Projects\Sprints\UtilityAnalyzerPerf\Benchmark\Projects\akka.net\src\Akka.sln" /a CopyPasteTokenAnalyzer /a FileMetadataAnalyzer /a LogAnalyzer /a MetricsAnalyzer /a SymbolReferenceAnalyzer /a TokenTypeAnalyzer
AWS SDK
Measurement details
TODO: