3 ms·
Javas GCs already achieve their goals. The JVM has several GCs to select from based on the needs such as: high throughput, very large heap sizes (up to the TB r
by apta 7y ago
Javas GCs already achieve their goals. The JVM has several GCs to select from based on the needs such as: high throughput, very large heap sizes (up to the TB range), and there are two in experimental phase for very low latencies (ZGC and Shenandoah).
- hu3 7y ago> Javas GCs already achieve their goals. So does Go. Otherwise it wouldn't be anywhere as popular specially with regards to server-side usage by giants of the industry.
- pjmlp 7y agoGoogle's stamp helps. Java GC don't need allocation tricks of several GBs, like Twich was forced to do.
- tick_tock_tick 7y agoTwitch did that since they preferred to use code over environment configuration. They could have achieved similar results using the GOGC environment variable but didn't want too; They even said so in there post.
- lightgreen 7y ago> very large heap sizes It is not heap size that matters, but how often old objects are mutated. Basically, if you have 1TB of immutable objects, you are lucky, but if you constantly modify all the heap, then you will have a lot of headache. GC authors continuously mislead on this issue for many years (they promised the same with multi gigabyte heaps but with G1 several years ago).