[11u] Backport JEP 346 : Promptly Return Unused Committed Memory from G1
rbruno at gsd.inesc-id.pt
Tue Apr 7 11:42:20 UTC 2020
I globally agree with most of the discussion so far.
Just trying to answer Gil's question on why we want this in JDK11u; I think
the main reason is that JDK11 is the current LST and the next one is still
>1year away. IMHO and experience, people in the Java community tend to
extensively rely on libraries and code that was not developed by
themselves. A great percentage of this code is not updated regularly to
keep up with non-LTS JDK releases and trying to move your project to a more
recent JDK release is a huge headache, especially in large projects with
100s of dependencies. I've been in several projects where people are
reluctant to deploy production code in non-LTS JDKs...
Andrew also mentioned the problem of testing experimental releases. I think
here this is not a problem since we have two industry companies advocating
for this patch. Would Alibaba and Jelastic be available to deploy an
experimental version of JDK11u with this JEP? If so, maybe after a couple
of months there would be enough convincing evidence that this JEP won't
break anything significant.
Andrew Haley <aph at redhat.com> escreveu no dia terça, 7/04/2020 à(s) 12:51:
> On 4/7/20 11:30 AM, Liang Mao wrote:
> > But if a feature has been tested through several releases(the JEP
> > and related bug fixes were pushed in JDK12/13), we are able to take
> > it into the consideration as a stable change. Anyway, do you think
> > we shall get some more technical comments from Thomas before make
> > the decision?
> I think we should keep talking. As far as I'm concerned this is still
> a live issue for discussion, but I made my points in
> Andrew Haley (he/him)
> Java Platform Lead Engineer
> Red Hat UK Ltd. <https://www.redhat.com>
> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
More information about the jdk-updates-dev