RFR: 8339114: DaCapo xalan performance with -XX:+UseObjectMonitorTable [v3]

[Roman Kennke]

> - When successfully looked up an OM in the OMCache, then make it avaiable in the BasicLock cache. Use that cache whenever possible.
> - When successfully looked up an OM in the OMCache, then don't push-back the OM on that cache to avoid shuffling the cache on each monitor enter.
> - In the runtime path of monitorexit, attempt to use the BasicLock cache, then the OMCache, and only look up in the table when the caches failed.
> - Some small code shufflings.
> 
> I did 50 runs of xalan, each of which do 10 warmup iterations before doing one measurement. The following results are the averages of the measurement iterations across the 50 runs:
> without-OMT: 773.3 ms
> with-OMT: 797.28 ms
> 
> That is still a regression of ~3%

Roman Kennke has updated the pull request incrementally with one additional commit since the last revision:

  Include objectMonitor.inline.hpp

-------------

Changes:
  - all: https://git.openjdk.org/jdk/pull/24098/files
  - new: https://git.openjdk.org/jdk/pull/24098/files/15a54aa0..fc5062a4

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=24098&range=02
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=24098&range=01-02

  Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod
  Patch: https://git.openjdk.org/jdk/pull/24098.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/24098/head:pull/24098

PR: https://git.openjdk.org/jdk/pull/24098