Support benchmark-specific PERF_ITERATIONS from perfConfig.json (#6409)

This patch allows each benchmark in perfConfig.json to define its own PERF_ITERATIONS.
If not specified, it falls back to the global parameter or default value (4).

Fixes: #6381

Signed-off-by: Phat Diep  <[email protected]>

Author: phdiep2003

buildenv/jenkins/perfPipeline_root.groovy

@@ -63,6 +63,7 @@ node("worker || (ci.role.test&&hw.arch.x86&&sw.os.linux)") {
                 baseParams << string(name: "BENCHMARK", value: item.BENCHMARK)
                 baseParams << string(name: "TARGET", value: item.TARGET)
                 baseParams << string(name: "BUILD_LIST", value: item.BUILD_LIST)
+                baseParams << string(name: "PERF_ITERATIONS", value: item.PERF_ITERATIONS ? item.PERF_ITERATIONS.toString() : "4")
 
                 item.PLAT_MACHINE_MAP.each { kv -> 
                         kv.each {p, m -> 

perf/config/hotspot/perfConfig.json

@@ -3,6 +3,7 @@
         "BENCHMARK":"dacapo",
         "TARGET": "testList TESTLIST=dacapo-h2,dacapo-avrora,dacapo-fop,dacapo-luindex,dacapo-pmd,dacapo-sunflow,dacapo-xalan",
         "BUILD_LIST": "perf/dacapo",
+        "PERF_ITERATIONS": 3,
         "PLAT_MACHINE_MAP":[
             {"x86-64_linux": "hw.arch.x86&&sw.os.linux&&ci.role.perf"}
         ]