Taking long time to show estimated time in progress report

[adarshnd14]

Question

1. Need to know why Stryker is taking long time for even to get the in-progress report with estimation time for large JavaScript projects. And are there any work around for this.
2. Even if we reduce the concurrency the CPU utilization is hitting peak. Why is Stryker not limiting the CPU utilization based on the concurrency mentioned.

Context: We are trying to run mutation test on JavaScript projects which are having 16000 to 20000 mutants. As we were not able to get the in-progress metrics for such projects in our local machine with 16 GB RAM because the machine was getting hanged, we tried it in AWS EC2 m5.24xlarge instance which is having 96v CPU. But still even after waiting for 30min we are unable to get the estimated time for completion and no mutants got killed or survived till then.

Stryker environment

+-- @stryker-mutator/core@4.6.0 with stryker-cli@1.0.1

Stryker config used

{
 packageManager: "npm",
 reporters: ["html", "clear-text", "progress", "json"] ,
 concurrency : 74, // for 96v CPU machine
 testRunner" "command",
 coverageAnalysis: "off",
 timeoutMS: 1000000
}

+-- jest@26.6.2 or above

Additional context

We have tried running with testRunner as "jest" and coverageAnalysis as "perTest" but it is not working out for all the repositories. So, we are going with the above mentioned configuration where the mutation test is running fine but we are not able to get even the time estimate that we get with "progress" report for the larger projects.