Support PERF_ITERATIONS in perfConfig#6409
Conversation
74664f2 to
0a36c68
Compare
|
@phdiep2003 could you please resolve the merge conflicts and do not include other people's commits in your PR? Thanks |
Thank you, I was about to ask you the question. I will do it now! |
0a36c68 to
03d06c8
Compare
@llxia I have resolved the conflicts |
|
Please keep PERF_ITERATIONS in the perfConfig.json file. Thanks |
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: adoptium#6381 Signed-off-by: Phat Diep <phdiep@andrew.cmu.edu>
03d06c8 to
92c754c
Compare
|
Why 3 as a default in pnce place and 4 in another? |
The perfConfig.json file is a benchmark-specific configuration file. If user don't specified PERF_ITERATIONS, the default value of 4 will be used by the performance pipeline. I chose 3 for the distinction with the default value. |
Fix: #6381
Tested: https://ci.adoptium.net/view/Test_grinder/job/Perf_Pipeline/96/