On 2/11/20 11:49 AM, [email protected] wrote:
Ralf,
I see this feature adds a lot of code. In fact, I'm not sure, it is
worth to add this kind of complexity (including new compressing
threads) into the VM implementation. What is a real use case behind
it? Could this compressing be done separately from VM implementation?
I have to say that the very same thoughts were also occurring to me ...
Thanks,
Serguei
On 2/11/20 11:41 AM, [email protected] wrote:
Hi Ralf,
I'd suggest for the option format something like this:
-gz[=level]
where level is an int. The part [=level] is optional.
The level is 0 by default (if it is not set).
Thanks,
Serguei
On 2/11/20 7:35 AM, Schmelter, Ralf wrote:
Hi Yasumasa,
I think I've tried too much by using the -gz flag as a boolean plus
a int value. I've decided to use two options instead: -gz as a
boolean option to turn compression on and -gz-level to specify the
compression level. E.g.
GC.heap_dump -gz -gz-level=3 test.hprof.gz
Best regards,
Ralf
