3 ms·
Azul has a JVM that doesn't have GC pauses and has fairly good memory allocation / collection throughput.
by scheme271 1y ago
Azul has a JVM that doesn't have GC pauses and has fairly good memory allocation / collection throughput.
- throwaway2037 1y ago> Azul has a JVM that doesn't have GC pauses Unless GC is disabled, all GC has some pauses. You can see the chart of Azul GC pauses here: https://medium.com/@jadsarmo/why-we-chose-java-for-our-high-frequency-trading-application-600f7c04da94 https://medium.com/@jadsarmo/why-we-chose-java-for-our-high-... -> https://miro.medium.com/v2/resize:fit:1400/format:webp/1*yRG60eOIN9Yp8cjVW_vokA.png https://miro.medium.com/v2/resize:fit:1400/format:webp/1*yRG...
- scheme271 1y agoThat's GC duration time but the article indicates: "This is because Zing uses a unique collector called C4 (Continuously Concurrent Compacting Collector) that allows pauseless garbage collection regardless of the Java heap size (up to 8 Terabytes)." Azul's GC runs concurrrently with the app so those GC durations occur without a pause. If you think about it, there's no reason why GC requires a pause in order to work, with the right conditions, GC should be able to analyze and remove dead allocations without stopping an app.