< prev index next >

src/hotspot/share/prims/jvmti.xml

Print this page
rev 49264 : [mq]: event-only
rev 49265 : [mq]: event3
rev 49266 : [mq]: event4
rev 49267 : [mq]: event5
rev 49268 : [mq]: event6
rev 49269 : [mq]: event7

*** 13563,13573 **** </event> <event label="Sampled Object Allocation" id="SampledObjectAlloc" const="JVMTI_EVENT_SAMPLED_OBJECT_ALLOC" num="86" since="11"> <description> ! Sent when an object is sampled via the <internallink id="heap_monitoring"> Heap Sampling Monitoring system </internallink>. <p/> By default, the sampling rate used is geometric variable with a 512kb mean, meaning one object every 512k bytes, in average, per thread will provoke a callback. Each thread having its own internal allocation count, each thread will be sampling --- 13563,13573 ---- </event> <event label="Sampled Object Allocation" id="SampledObjectAlloc" const="JVMTI_EVENT_SAMPLED_OBJECT_ALLOC" num="86" since="11"> <description> ! Sent when an allocated object is sampled via the <internallink id="heap_monitoring"> Heap Sampling Monitoring system </internallink>. <p/> By default, the sampling rate used is geometric variable with a 512kb mean, meaning one object every 512k bytes, in average, per thread will provoke a callback. Each thread having its own internal allocation count, each thread will be sampling
*** 13575,13585 **** <p/> If another sampling rate is required, the user can call <functionlink id="SetHeapSamplingRate"></functionlink> with a strictly positive integer value, representing the new sampling rate to be used by the default sampler. <p/> ! This event is sent once the allocation has been done and provides the object, stack trace for the allocation, the thread allocating, the size of allocation, and class. <p/> Typical use cases of this system is to determine where most heap allocation are originating from. Using this in conjunction of weak references and the function <functionlink id="GetStackTrace"></functionlink>, a user can track which objects were allocated from which --- 13575,13585 ---- <p/> If another sampling rate is required, the user can call <functionlink id="SetHeapSamplingRate"></functionlink> with a strictly positive integer value, representing the new sampling rate to be used by the default sampler. <p/> ! This event is sent once the sampled allocation has been done and provides the object, stack trace for the allocation, the thread allocating, the size of allocation, and class. <p/> Typical use cases of this system is to determine where most heap allocation are originating from. Using this in conjunction of weak references and the function <functionlink id="GetStackTrace"></functionlink>, a user can track which objects were allocated from which
< prev index next >