You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This discussion was converted from issue #2400 on January 15, 2021 08:35.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Description:
While doing the performance tests, I noticed, that we run PMD from CLI by default only with one thread. This is correct according to the documentation: https://pmd.github.io/latest/pmd_userdocs_cli_reference.html#threads
But, why don't we use the number of available cpus? That would make run PMD faster by default already...
We use "1" here:
pmd/pmd-core/src/main/java/net/sourceforge/pmd/cli/PMDParameters.java
Lines 54 to 56 in 130fee6
We use "all available CPUs" here:
pmd/pmd-core/src/main/java/net/sourceforge/pmd/PMDConfiguration.java
Line 85 in 130fee6
But this value is not used, when running from CLI, the value of PMDParameters overwrites it.
Are there any reasons, why we should not change this?
Beta Was this translation helpful? Give feedback.
All reactions