I wasted weeks hand optimizing assembly because I benchmarked on random data

Re:I wasted weeks hand optimizing assembly because I benchma... by scheme271 on Thursday July 24, 2025 @09:01PM (#44678281)

Azul has a JVM that doesn't have GC pauses and has fairly good memory allocation / collection throughput.

[ Parent | on HN ]

Re:I wasted weeks hand optimizing assembly because I benchma... by throwaway2037 on Friday July 25, 2025 @02:32PM (#44686593)

    > 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-... -> https://miro.medium.com/v2/resize:fit:1400/format:webp/1*yRG...

[ Parent | on HN ]

Re:I wasted weeks hand optimizing assembly because I benchma... by scheme271 on Saturday July 26, 2025 @05:53PM (#44697212)

That'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.

[ Parent | on HN ]