-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
Fix Understood
In JDK-8314438 we have a very nice synthetic benchmark that can be used to measure speed performance of unsafe malloc.
However, we need a benchmark that measures the memory used by NMT as well, and for that we need to drop into native code on the VM level.
Here I propose a mechanism to record all the NMT requests to allocate the memory, which can be later used to "replay" it to measure performance that is as close to the real thing as possible.
Because we will be recording the memory allocation requests on the VM level, we will be able to retain the size of the memory requested and compare that to the actual chunk returned by the OS malloc, that we can use to find the "overhead".
Speed wise, this will allow us to focus on just the cost of the memory allocations, isolating the results from everything else that is going on in the VM at the time, that could affect the performance.
However, we need a benchmark that measures the memory used by NMT as well, and for that we need to drop into native code on the VM level.
Here I propose a mechanism to record all the NMT requests to allocate the memory, which can be later used to "replay" it to measure performance that is as close to the real thing as possible.
Because we will be recording the memory allocation requests on the VM level, we will be able to retain the size of the memory requested and compare that to the actual chunk returned by the OS malloc, that we can use to find the "overhead".
Speed wise, this will allow us to focus on just the cost of the memory allocations, isolating the results from everything else that is going on in the VM at the time, that could affect the performance.
- blocks
-
-
- Open
-
-
-
- Open
-
-
-
- In Progress
-
- relates to
-
-
- Resolved
-
-
-
- Closed
-
- links to
-
Review(master)
openjdk/jdk/23115
(1 links to)