Question regarding JEP 8204089 Timely Reducing Unused Committed Memory (original) (raw)

Sunny Chan, CLSA sunny.chan at clsa.com
Mon Jun 4 02:00:23 UTC 2018

Replied inline.

From: Ruslan Synytsky [mailto:synytskyy at jelastic.com] Sent: Friday, June 1, 2018 9:22 PM To: Sunny Chan, CLSA <sunny.chan at clsa.com> Cc: rbruno at gsd.inesc-id.pt; hotspot-gc-dev at openjdk.java.net; synytskyy at jelastic.com Subject: Re: Question regarding JEP 8204089 Timely Reducing Unused Committed Memory

Hi Sunny.

On 1 June 2018 at 07:36, Sunny Chan, CLSA <sunny.chan at clsa.com<mailto:sunny.chan at clsa.com>> wrote: Hello,

I have a number of question about the proposed changes for the JEP and I would like to make the following suggestions and comments

  1.  Are we planning to make this change the default behavior for G1? Or this is an optional switch for people who runs in a container environment?

Optional. It will be enough for beginning.

You say “enough for the beginning” – do you want to change them to be the default at some point?

Please document this in the JEP and highlight that this is optional.

  1.  In a trading systems, sometimes there are period of quiescence and then suddenly a burst of activity towards market close or market event. The loadavg you suggest to “monitor” the activity in the system only reports up to 14mins and it might not necessary a good measure for this type of applications, especially you would trigger a Full GC

I'm sure certain number of workloads can't afford it. Such kind of projects or other mission critical environments simply should not use this option.

  1.  You haven’t fill in the details for “The GCFrequency value is ignored and therefore, i.e., no full collection is triggered, if:”

Thanks. It's a missed part. Here are the "if" rules:

The doc will be updated.

  1.  If we are trigging full GC with this we should make sure the GC reason is populated and log properly in the GC log so we can track it down.

Good point.

I would like to see this as a goal in the JEP, and this should be clearly documented how people can track down GC caused by the flag.

  1.  I have not heard of J9 Gencon/Shenandoah providing similar functionality. Can you point me to further documentation on which feature you model upon?

What we know so far that OpenJ9 provides

Thank you

Thanks.

Sunny Chan Senior Lead Engineer, Executive Services D +852 2600 8907 | M +852 6386 1835 | T +852 2600 8888 5/F, One Island East, 18 Westlands Road<https://maps.google.com/?q=18+Westlands+Road&entry=gmail&source=g>, Island East, Hong Kong

[:1. Social Media Icons:CLSA_Social Media Icons_linkedin.png]<https://hk.linkedin.com/company/clsa>[:1. Social Media Icons:CLSA_Social Media Icons_twitter.png]<https://twitter.com/clsainsights?lang=en>[:1. Social Media Icons:CLSA_Social Media Icons_youtube.png]<https://www.youtube.com/channel/UC0qWp_lLnOcRYmBlCNQgZKA>[:1. Social Media Icons:CLSA_Social Media Icons_facebook.png]<https://www.facebook.com/clsacommunity/>

clsa.com<https://www.clsa.com/> Insights. Liquidity. Capital.

[CLSA_RGB]<https://www.clsa.com/member>

A CITIC Securities Company

The content of this communication is intended for the recipient and is subject to CLSA Legal and Regulatory Notices. These can be viewed at https://www.clsa.com/disclaimer.html or sent to you upon request. Please consider before printing. CLSA is ISO14001 certified and committed to reducing its impact on the environment.

-- Ruslan CEO @ Jelastic<https://jelastic.com/> The content of this communication is intended for the recipient and is subject to CLSA Legal and Regulatory Notices. These can be viewed at https://www.clsa.com/disclaimer.html or sent to you upon request. Please consider before printing. CLSA is ISO14001 certified and committed to reducing its impact on the environment. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20180604/3abb8e8a/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1122 bytes Desc: image001.png URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20180604/3abb8e8a/image001.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 1206 bytes Desc: image002.png URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20180604/3abb8e8a/image002.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 1070 bytes Desc: image003.png URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20180604/3abb8e8a/image003.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 1024 bytes Desc: image004.png URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20180604/3abb8e8a/image004.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 4859 bytes Desc: image005.png URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20180604/3abb8e8a/image005.png>

More information about the hotspot-gc-dev mailing list