> The fix adds posting VmObjectAlloc events by Unsafe.allocateInstance(Class<?> > cls). The previous attempt to post event directly from > 'LibraryCallKit::inline_unsafe_allocate()' cause performance regression even > if jvmti event is not enabled. Some optimizations have been disabled just > because possible usage and escaping of newly allocated object. > So event posting is doing by returning to interpreter if events are enabled. > > I verified that that performance (run locally only) of > org.renaissance.jdk.streams.JmhScrabble.runOperation > doesn't change if events are not enabled. > > There might be other intrinsics like > 'LibraryCallKit::inline_unsafe_newArray()' where VM allocate memory. I'm > going to file separate issue to find and fix them. > > Many thanks to Tobias H. for proposed solution. > > Testing with all tiers.
Leonid Mesnik has updated the pull request incrementally with one additional commit since the last revision: combined jvmti code ------------- Changes: - all: https://git.openjdk.org/jdk/pull/15110/files - new: https://git.openjdk.org/jdk/pull/15110/files/07499679..5095114f Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=15110&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=15110&range=00-01 Stats: 38 lines in 1 file changed: 17 ins; 21 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/15110.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/15110/head:pull/15110 PR: https://git.openjdk.org/jdk/pull/15110
