3 ms·

You want to run a task from your build tool that has nothing to do with indexing before indexing finishes? No can do! You installed an npm package and it seems

You want to run a task from your build tool that has nothing to do with indexing before indexing finishes? No can do! You installed an npm package and it seems to depend on all the things? Let's start indexing on node_modules and give you no chance to even uninstall the **er. You used the CLI to work around our tooling? Hey let's start indexing immediately after this one finishes so it's a great idea for a coffee break, just never pull directly after coming back so you may actually do some work until we bog down all the cpu cores. Don't get me wrong, I love all the JB IDEs, but indexing has been a deal-breaker for many.

adrianmsmith 4y ago
> so you may actually do some work until we bog down all the cpu cores. I wish it bogged down all cores.. I work on relatively small Java projects (maybe 10 KLOC, 20 or so items in the pom.xml (although these obviously have transitive dependencies)). IntelliJ 2018 would re-index everything in a few minutes using all 20 vcores. I specifically spent about $8k on an iMac Pro back in the day to make this faster. IntelliJ 2022, on the other hand, uses only 4 cores, and takes about 10 minutes. That's a stupid default (if I buy a powerful computer I want to use it..). There is a setting to override it, but in my case it just doesn't work. CPU goes to approx 400% and just stays there. I filed a bug report, no movement.