JDK-8219392 : NMT: Move serviceability related allocation from mtInternal to mtServiceability
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: 13
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • Submitted: 2019-02-19
  • Updated: 2019-02-21
  • Resolved: 2019-02-20
Comments
Serviceability allocations are small. For example, - Serviceability (reserved=22KB, committed=22KB) (malloc=22KB #419) total 419 allocations reported in summary, but only 27 allocations show up in details, with total 4K out of 22K. [0x00007ffbb7c30a37] JavaThread::initialize()+0x237 [0x00007ffbb7c3128c] JavaThread::JavaThread(void (*)(JavaThread*, Thread*), unsigned long)+0xac [0x00007ffbb73dfc3b] JVM_StartThread+0x20b [0x00007ffb788bb6ab] (malloc=3KB type=Serviceability #11) [0x00007ffbb78d9342] PerfDataManager::create_long_variable(CounterNS, char const*, PerfData::Units, long, Thread*)+0x32 [0x00007ffbb6a1ae19] AgeTable::AgeTable(bool)+0x1b9 [0x00007ffbb70ff751] G1Policy::create_policy(G1CollectorPolicy*, STWGCTimer*)+0x71 [0x00007ffbb7070235] G1CollectedHeap::G1CollectedHeap(G1CollectorPolicy*)+0x385 (malloc=1KB type=Serviceability #16) It probably leads to more confusion than help. I am leaning to not adding serviceability.
21-02-2019