RFR(XS): 8193521: glibc wastes memory with default configuration
aph at redhat.com
Thu Dec 14 18:01:30 UTC 2017
On 14/12/17 16:00, Doerr, Martin wrote:
> I'm not aware of performance critical concurrent malloc usages in the JVM. Maybe somebody else is?
> Comments are welcome. I will also need a sponsor if this change is desired.
Is this something that a JVM should decide? I would have thought it's
for the user of the system to decide policy. They can set
MALLOC_ARENA_MAX on a system-wide basis if they really need to save
memory, or just for Java. Or are you suggesting that Java is so
unusual that it justifies overriding a user's settings?
If a user has explicitly set MALLOC_ARENA_MAX, don't futz with it.
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 hotspot-runtime-dev