[omworld-jdk] RFR: 8326823: Lilliput: OMWorld: Separate NMT category

[Axel Boldt-Christmas]

On Tue, 27 Feb 2024 10:39:54 GMT, Roman Kennke <rkennke at openjdk.org> wrote:

> Currently, the OMWorld table uses mtThread NMT category, which seems very wrong. We could instead add it into the mtObjectMonitor or mtSynchronizer categories, but I think it would be more useful to give the table its own category, for measuring overhead and also compare it to ObjectSynchronizer.
> 
> Example NMT output would look like:
> 
> 
> -           Object Monitors (reserved=1750823568, committed=1750823568)
>                            (malloc=1750823568 #8417421) (peak=1958719776 #9416922)
> -                  OM World (reserved=151456088, committed=151456088)
>                            (malloc=151456088 #8417425) (peak=152173976 #8462293)

Looks good.

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

Marked as reviewed by aboldtch (Reviewer).

PR Review: https://git.openjdk.org/lilliput/pull/141#pullrequestreview-1903756419