While working on https://bugs.openjdk.org/browse/JDK-8317453 I noticed that PrintNMTStatistics reports back the "requested" memory size. However, NMT adds additional 20 bytes for the header and footer and OS will next round the size up to fit its memory allocation bucket, so when we report X bytes in reality it's at least X+20, and often way more (especially on macOS) than that.

Any comparison between what VM currently reports and what native tools like pmap report will be way off, making PrintNMTStatistics less useful than expected and confusing.