Hi Natchanon,
Yes, they are. Sorry for the confusion.
Regarding your analysis speed, from the logs, it looks like resources are not the problem. There seems to be plenty of disk, memory and CPU available.
I see that the time is all taken in analysis of TypeScript files. Is there a tsconfig.json file in your project? If so, could you post it, redacted as necessary? And this thread may be relevant.
Also, could you tell us how many Lines of Code your project has?
As a side note, I see that you’re using
- SonarQube 10.1
- Java 11
- SonarScanner 4.8.1
All of those are a bit dusty. Current versions are
- SonarQube 10.4.1 (which requires Java 17)
- SonarScanner 5.0.1 (which embeds Java 17)
And by the time you get to SonarQube 10.4.1, Node.js is embedded as well, so that may be helpful.
I don’t believe these upgrades will impact your analysis time, but it’s incumbent on me to mention them.
Ann