[omworld-jdk] Integrated: 8326823: Lilliput: OMWorld: Separate NMT category
Roman Kennke
rkennke at openjdk.org
Tue Feb 27 19:06:02 UTC 2024
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)
This pull request has now been integrated.
Changeset: 9c09cda0
Author: Roman Kennke <rkennke at openjdk.org>
URL: https://git.openjdk.org/lilliput/commit/9c09cda04e9bbdd0611e0ff567421f68d31821d7
Stats: 4 lines in 2 files changed: 1 ins; 0 del; 3 mod
8326823: Lilliput: OMWorld: Separate NMT category
Reviewed-by: aboldtch
-------------
PR: https://git.openjdk.org/lilliput/pull/141
More information about the lilliput-dev
mailing list