Currently when jenkins runs compare-compilers.sh and compare-optimizer.sh, they end up running runPerformanceTest.py with no -j argument, so the resulting builds end up running -j80 or something (from number of CPUs), while in fact they only have access to 4 cores (as set with PARALLEL in jenkins env). As such the builds are running quite slowly. This should hopefully help.
Currently when jenkins runs
compare-compilers.shandcompare-optimizer.sh, they end up runningrunPerformanceTest.pywith no-jargument, so the resulting builds end up running-j80or something (from number of CPUs), while in fact they only have access to 4 cores (as set withPARALLELin jenkins env). As such the builds are running quite slowly. This should hopefully help.Copyright and Licensing
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the BSD 3-clause license (https://opensource.org/licenses/BSD-3-Clause)