<br>I am posting this to hotspot-gc-use, but the idea is that it also post to -dev (but given how<br>the lists are arranged, I am posting directly to the one and not the other to avoid double copies<br>to those who are in the intersection of the two kists, while covering those in the union of the two).<br>
<br>I've noticed recently in my use of the the class histogram feature, that in typical cases I am interested<br>in the top few types of objects and not in the long thin tail. I am not sure how typical my use or<br>experience is, but it would appear to me (based on my limited experience of late) that if we limited<br>
the histogram output to the top "N" (for say N = 40 or so) classes by default, it would likely satisfy<br>80-90% of use cases. For the remaining 10% of use cases, one would provide a complete dump,<br>or a dump with more entries than available by default. <br>
<br>I wanted to run this suggestion by everyone and see whether this would have some traction<br>wrt such a request.<br><br>I am guessing that this may be especially useful when dealing with very large applications that<br>
may have many different types of objects in the heap and might present a very long thin (and in<br>many cases uninteresting) tail. (There may be other ways of restricting the output, for example<br>by cutting off output below a certain population or volume threshold, but simply displaying the<br>
top N most voluminous or populous classes would seem to be the simplest....)<br><br>Comments?<br>-- ramki<br><br><br>