Integrated: 8339114: DaCapo xalan performance with -XX:+UseObjectMonitorTable

[Roman Kennke]

On Tue, 18 Mar 2025 12:41:44 GMT, Roman Kennke <rkennke at openjdk.org> wrote:

> - 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%

This pull request has now been integrated.

Changeset: 49cb7aaa
Author:    Roman Kennke <rkennke at openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/49cb7aaad903aa5209da9f4af4b484ff38c0fb8b
Stats:     63 lines in 8 files changed: 37 ins; 6 del; 20 mod

8339114: DaCapo xalan performance with -XX:+UseObjectMonitorTable

Reviewed-by: coleenp, aboldtch

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

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