Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Extension causes high cpu load

See original GitHub issue

Issue Type: Performance
Extension Name: vscode-jest
Extension Version: 2.9.2
OS Version: Linux x64 4.18.0-18-generic
VSCode version: 1.33.1

⚠️ Make sure to attach this file from your home-directory: ⚠️/home/lexy/Orta.vscode-jest-unresponsive.cpuprofile.txt

Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Issue Analytics

State:
Created 4 years ago
Comments:10 (1 by maintainers)

Top GitHub Comments

1reaction

franklin-rosscommented, Jan 9, 2020

So personally I think this is just because it spawns a metric arse load of workers. More than I have cores, which seems strange. I’m not using any snapshots. I looked pretty hard for a way to specify the --maxWorkers=<num>|<string> option to the extension, but couldn’t see a way. Maybe adding that as an option would give us some control at least?

I guess it’s spawning one less than the number of virtual cores, which is the default for jest. The problem is there’s often a lot of other things going on, like language servers, linters, etc. or I have a couple of instances of VSCode open, all running tests. I’d much prefer this to be lower by default. In fact, Jest in watch mode apparently defaults to half the available cores for this reason.

0reactions

rue-mishakorablincommented, Jun 9, 2020

Are there any updates to this?