12 ms·
So Go set Heap to 2X and CPU 25% as GC overhead. In Java side may be due to generational/copying GC Heap is recommended 3-4X and CPU ~20%. This is good read ab
by geodel 8y ago
So Go set Heap to 2X and CPU 25% as GC overhead. In Java side may be due to generational/copying GC Heap is recommended 3-4X and CPU ~20%. This is good read about Java GC tuning:
https://engineering.linkedin.com/garbage-collection/garbage-collection-optimization-high-throughput-and-low-latency-java-applications https://engineering.linkedin.com/garbage-collection/garbage-...
- the8472 8y agoThe article you're linking to is outdated. It talks about java 7 and CMS, which is deprecated as of OpenJDK9. There are other collectors in OpenJDK and then there are other JVMs too. They all come with a lot of different overhead, complexity, latency and throughput tradeoffs.