The ByteBuffers micro benchmark seems to be a little dated. It should be a useful resource to leverage when analysing the performance impact of any potential implementation changes in the byte buffer classes. More specifically, the impact of such changes on the performance of sharp memory access operations.
This issue proposes to update the benchmark in the following ways to meet the aforementioned use-case: 1. Remove allocation from the individual benchmarks - it just creates noise. 2. Consolidate per-thread shared heap and direct buffers. 3. All scenarios now use absolute memory access operations - so no state of the shared buffers is considered. 4. Provide more reasonable default fork, warmup, etc, out-of-the-box. 5. There seems to have been an existing bug in the test where the size parameter was not always considered - this is now fixed. ------------- Commit messages: - Initial changes Changes: https://git.openjdk.java.net/jdk/pull/1430/files Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=1430&range=00 Issue: https://bugs.openjdk.java.net/browse/JDK-8257074 Stats: 69 lines in 1 file changed: 22 ins; 14 del; 33 mod Patch: https://git.openjdk.java.net/jdk/pull/1430.diff Fetch: git fetch https://git.openjdk.java.net/jdk pull/1430/head:pull/1430 PR: https://git.openjdk.java.net/jdk/pull/1430
