RFR 8217518: Crypto benchmarks not warming up in time
adam.petcher at oracle.com
Tue Jan 22 15:24:22 UTC 2019
Please review this very small change that adds the "+AlwaysPreTouch"
option to the crypto benchmarks to allow them to warm up in time. This
fix is in response to Eric's discovery (when reviewing the new
benchmarks for KeyAgreement and Cipher) that the crypto benchmarks were
not warming up very well. Sergey discovered that the cause is memory
allocation overhead with large heaps and G1. Adding +AlwaysPreTouch does
more of this memory allocation work up front so it doesn't interfere
with the benchmark.
More information about the jdk-dev