*Date: *Saturday, December 14, 2019 at 2:46 AM
*To: *"linzang(臧琳)" mailto:linz...@tencent.com>>,
"serviceability-dev@openjdk.java.net<mailto:serviceability-dev@openjdk.java.net>"
mailto:serviceability-dev@openjdk.java.net>>
*Subject: *Re: Discuss the design of
output?
Yes, the incremental dump information shows the number of the objects
and the totally bytes have been iterated.
Thanks!
BRs,
Lin
*From: *Chris Plummer
*Date: *Saturday, December 14, 2019 at 2:46 AM
*To: *"linzang(臧琳)" ,
"serviceability-dev@openjdk.java.net"
ut?
Yes, the incremental dump information shows the number of the objects and the
totally bytes have been iterated.
Thanks!
BRs,
Lin
From: Chris Plummer
Date: Saturday, December 14, 2019 at 2:46 AM
To: "linzang(臧琳)" , "serviceability-dev@openjdk.java.net"
Subject: Re: Discuss
Hi Lin,
I have a question regarding the need for incremental support. The
CSR states:
Problem: Now, the "JMap -histo" tool can not dump intermediate
result, which is useful if the heap is large and dumping the whole
heap can be stuck.
Dear All,
I want to re-activate the thread of discussion about the implementation of
parallel and incremental “Jmap -histo”.
The target of these changes is to solve the problems that “jmap -histo” may
“ timeout or killed by timer” when heap is large. And the result of “jmap
-histo” is “on
