Problem Description
DigestBench and HMACBench seem to take forever to run. Benchmarks in BumbleBench usually take less than 2 mins. I had to abort DigestBench run after it kept running for 1 hr 45 min, generating an extremely large output (> 3 GB) as shown in the screenshots below. HMACBench behaves in a similar way.
I'm trying to add these BumbleBench targets for testing at Adopt as part of adoptium/aqa-tests#1379.
Console Output
13:55:45 ===============================================
13:55:45 Running test bumbleBench-DigestBench_0 ...
13:55:45 ===============================================
13:55:45 bumbleBench-DigestBench_0 Start Time: Fri Nov 1 13:55:43 2019 Epoch Time (ms): 1572630943888
13:55:45 "/java/jenkins/workspace/Piyush-Grinder/openjdkbinary/j2sdk-image/bin/java" -Xshareclasses:destroyAll; "/java/jenkins/workspace/Piyush-Grinder/openjdkbinary/j2sdk-image/bin/java" -Xshareclasses:groupAccess,destroyAll; echo "cache cleanup done";
13:55:45 JVMSHRC005I No shared class caches available
13:55:45 JVMSHRC005I No shared class caches available
13:55:45 cache cleanup done
13:55:45 variation: NoOptions
13:55:45 JVM_OPTIONS: -Xcompressedrefs
13:55:45 { itercnt=1; \
13:55:45 mkdir -p "/java/jenkins/workspace/Piyush-Grinder/openjdk-tests/TestConfig/../TestConfig/test_output_15726308899881/bumbleBench-DigestBench_0"; \
13:55:45 cd "/java/jenkins/workspace/Piyush-Grinder/openjdk-tests/TestConfig/../TestConfig/test_output_15726308899881/bumbleBench-DigestBench_0"; \
13:55:45 "/java/jenkins/workspace/Piyush-Grinder/openjdkbinary/j2sdk-image/bin/java" -jar /java/jenkins/workspace/Piyush-Grinder/openjdk-tests/TestConfig/../../jvmtest/perf/bumbleBench/bumblebench/BumbleBench.jar DigestBench; \
13:55:45 if [ $? -eq 0 ] ; then echo ""; echo "bumbleBench-DigestBench_0""_PASSED"; echo ""; cd /java/jenkins/workspace/Piyush-Grinder/openjdk-tests/TestConfig/..; else echo ""; echo "bumbleBench-DigestBench_0""_FAILED"; echo ""; fi; } 2>&1 | tee -a "/java/jenkins/workspace/Piyush-Grinder/openjdk-tests/TestConfig/../TestConfig/test_output_15726308899881/TestTargetResult";
13:55:45 Using Provider SUN
13:55:45 Payload size: 4096 bytes
13:55:45
13:55:45 -= BumbleBench series 7 version 5.10 running DigestBench Fri Nov 01 13:55:44 EDT 2019 =-
13:55:45
13:55:45 Target Est Uncert% MaxPeak Peak Peak% %paused
13:55:45 0.0s: < 110 100 12.0 -inf -inf --
13:55:45 0.0s: <! 94 88 14.4 -inf -inf --
13:55:45 0.0s: <! 81.66 75.33 17.3 -inf -inf --
13:55:45 0.0s: <! 68.82 62.31 20.7 -inf -inf --
13:55:45 0.0s: <! 55.85 49.39 24.9 -inf -inf --
13:55:45 0.0s: <! 43.25 37.10 29.9 -inf -inf --
13:55:45 0.0s: <! 31.56 26.02 35.8 -inf -inf --
13:55:45 0.0s: <! 21.36 16.70 40.0 -inf -inf --
13:55:45 0.0s: <! 13.36 10.02 40.0 -inf -inf --
13:55:45 0.0s: <! 8.015 6.011 40.0 -inf -inf --
13:55:45 0.0s: <! 4.809 3.607 40.0 -inf -inf --
13:55:45 0.0s: <! 2.885 2.164 40.0 -inf -inf --
13:55:45 0.0s: <! 1.731 1.298 40.0 -inf -inf --
13:55:45 0.0s: <! 1.039 0.7791 40.0 -inf -inf --
13:55:45 0.0s: <! 0.6233 0.4674 40.0 -inf -inf --
13:55:45 0.0s: <! 0.3740 0.2805 40.0 -inf -inf --
13:55:45 0.0s: <! 0.2244 0.1683 40.0 -inf -inf --
13:55:45 0.0s: <! 0.1346 0.1010 40.0 -inf -inf --
13:55:45 0.0s: <! 0.08077 0.06058 40.0 -inf -inf --
13:55:45 0.0s: <! 0.04846 0.03635 40.0 -inf -inf --
13:55:45 0.0s: <! 0.02908 0.02181 40.0 -inf -inf --
13:55:45 0.0s: <! 0.01745 0.01309 40.0 -inf -inf --
13:55:45 0.0s: <! 0.01047 0.007851 40.0 -inf -inf --
13:55:45 0.0s: <! 0.006281 0.004711 40.0 -inf -inf --
13:55:45 0.0s: <! 0.003769 0.002826 40.0 -inf -inf --
13:55:45 0.0s: <! 0.002261 0.001696 40.0 -inf -inf --
13:55:45 0.0s: <! 0.001357 0.001018 40.0 -inf -inf --
13:55:45 0.0s: <! 0.0008140 0.0006105 40.0 -inf -inf --
13:55:45 0.0s: <! 0.0004884 0.0003663 40.0 -inf -inf --
13:55:45 0.0s: <! 0.0002930 0.0002198 40.0 -inf -inf --
13:55:45 0.0s: <! 0.0001758 0.0001319 40.0 -inf -inf --
13:55:45 0.0s: <! 0.0001055 0.00007912 40.0 -inf -inf --
13:55:45 0.0s: <! 0.00006330 0.00004747 40.0 -inf -inf --
13:55:45 0.0s: <! 0.00003798 0.00002848 40.0 -inf -inf --
13:55:45 0.0s: <! 0.00002279 0.00001709 40.0 -inf -inf --
13:55:45 0.0s: <! 0.00001367 0.00001025 40.0 -inf -inf --
13:55:45 0.0s: <! 0.000008203 0.000006153 40.0 -inf -inf --
13:55:45 0.0s: <! 0.000004922 0.000003692 40.0 -inf -inf --
13:55:45 0.0s: <! 0.000002953 0.000002215 40.0 -inf -inf --
13:55:45 0.0s: <! 0.000001772 0.000001329 40.0 -inf -inf --
13:55:45 0.0s: <! 0.000001063 797.4n 40.0 -inf -inf --
13:55:45 0.0s: <! 637.9n 478.4n 40.0 -inf -inf --
13:55:45 0.0s: <! 382.7n 287.1n 40.0 -inf -inf --
...
...
To Reproduce
Problem Description
DigestBench and HMACBench seem to take forever to run. Benchmarks in BumbleBench usually take less than 2 mins. I had to abort DigestBench run after it kept running for 1 hr 45 min, generating an extremely large output (> 3 GB) as shown in the screenshots below. HMACBench behaves in a similar way.
I'm trying to add these BumbleBench targets for testing at Adopt as part of adoptium/aqa-tests#1379.
Console Output
To Reproduce