News for hackers. Stuff that matters.
Re:Ryzen Threadripper Pro 3995WX Spotted by Xylakant on Friday July 10, 2020 @06:05AM (#23789844)
The underlying reason is that at around 32GB the JVM internally shifts from 32bit pointers for HEAP management to 64bit. The feature is called compressed object pointers (compressed oops) The increased pointer size uses substantial amounts of RAM, a reasonable estimate is that you need at least ~45GB to not have a loss in total available HEAP. Also, GC cycles get longer the more HEAP you have. However, some workloads may require more heap to even be possible and there’s pauseless garbage collector implementations able to handle substantial amounts of memory, so it is possible. It’s just not something you should be doing unless you know exactly what you are doing.

See https://wiki.openjdk.java.net/display/HotSpot/CompressedOops

Re:Ryzen Threadripper Pro 3995WX Spotted by reitzensteinm on Friday July 10, 2020 @06:24AM (#23789956)
Lacking value types, larger pointers will probably penalize JVM programs more than their peers.
Re:Ryzen Threadripper Pro 3995WX Spotted by SomewhatLikely on Friday July 10, 2020 @09:04AM (#23791041)
While there are no JEP 169 style Value Types, you can still layout your data in a way that significantly reduces the number of pointers. For example using parallel arrays of primitives. It's not as clean, but it is one mitigation.