There's currently 2 way to define the number of available processes:
SCANCODE_PROCESSES=4 for the scancode pipes (docker and rootfs pipelines)SCANCODE_DEFAULT_OPTIONS=--processes 4 for the scancode cli subprocess calls (scan_codebase and scan_package pipelines)
This is confusing for the user as you may think you set the proper settings but for some pipelines you are actually only running on 1 cpu.
Also, the default when SCANCODE_PROCESSES is not provided is to base the number of workers on the CPU count of the machine. But for the SCANCODE_DEFAULT_OPTIONS the default is always 1. We should have a similar default for both approaches.
There's currently 2 way to define the number of available processes:
SCANCODE_PROCESSES=4for thescancodepipes (dockerandrootfspipelines)SCANCODE_DEFAULT_OPTIONS=--processes 4for the scancode cli subprocess calls (scan_codebaseandscan_packagepipelines)This is confusing for the user as you may think you set the proper settings but for some pipelines you are actually only running on 1 cpu.
Also, the default when
SCANCODE_PROCESSESis not provided is to base the number of workers on the CPU count of the machine. But for theSCANCODE_DEFAULT_OPTIONSthe default is always 1. We should have a similar default for both approaches.