-
Bug
-
Resolution: Fixed
-
P3
-
None
-
None
There are noticeable performance regressions on both Linux and Windows that need to be investigated. They are each AES related:
• micro.benchmarks.crypto.small.AESBench.decrypt-algorithm:AES_CBC_NoPadding-dataSize:1024-keyLength:128-provider:
LXS: approx. -18%
WXS: approx. -3%
• micro.benchmarks.crypto.small.AESBench.decrypt-algorithm:AES_ECB_NoPadding-dataSize:1024-keyLength:128-provider:
LXS: approx. -8%
WXS: approx. -4%
• micro.benchmarks.crypto.small.AESGCMBench.decrypt-algorithm:AES_GCM_NoPadding-dataSize:1024-keyLength:128-provider:
LXS: approx. -3%
WXS: approx. -2%
The regressions reproduce when ran on the same machine (ie, triage).
The regressions reproduce when ran on a different machine (ie, re-traige).
A JVMswap run indicates the cause is in the JDK (ie, not the JVM).
• micro.benchmarks.crypto.small.AESBench.decrypt-algorithm:AES_CBC_NoPadding-dataSize:1024-keyLength:128-provider:
LXS: approx. -18%
WXS: approx. -3%
• micro.benchmarks.crypto.small.AESBench.decrypt-algorithm:AES_ECB_NoPadding-dataSize:1024-keyLength:128-provider:
LXS: approx. -8%
WXS: approx. -4%
• micro.benchmarks.crypto.small.AESGCMBench.decrypt-algorithm:AES_GCM_NoPadding-dataSize:1024-keyLength:128-provider:
LXS: approx. -3%
WXS: approx. -2%
The regressions reproduce when ran on the same machine (ie, triage).
The regressions reproduce when ran on a different machine (ie, re-traige).
A JVMswap run indicates the cause is in the JDK (ie, not the JVM).
- relates to
-
JDK-8209862 CipherCore performance improvement
- Resolved