Hi Andrew,
Thanks for your questions and sorry for my delayed response.
In order to be able to investigate this, we would need your help to see what is taking that long.
Could you please send us the logs for BEGIN step (as far as I understand the END doesn’t get to run due to the timeout) in verbose mode and also the dotnet build binary logs with the following parameters set: /p:reportanalyzer=true /v:d -bl:build.binlog.
/p:reportanalyzer=true /v:d parameters are needed to have relevant performance results included and -bl:build.binlog is needed to ensure binary logs are generated which helps us a lot.
Regarding the performance, from our measurements the memory size is not that relevant as the processor power. The compiler does a great job at scaling up, and using the resources available by running the analyzers concurrently. The differences in time are noticeable when increasing to 16GB or 32GB.
We also have a guide for troubleshooting performance related issues: The Sonar guide for investigating the performance of .NET analysis