4 ms·
It's known that golang optimizes for latency at the expense of throughput, and it doesn't give you the option to change this if your requirements change. This i
by apta 6y ago
It's known that golang optimizes for latency at the expense of throughput, and it doesn't give you the option to change this if your requirements change. This is the power of the JVM. In any case, the JVM now ships with ZGC, a low latency GC, and it may be worth running the benchmark with it. There's also another low latency GC in the works called Shenandoah.
- agallego 6y agoWe wrote it in c++ on top of seastar.io
- apta 6y agoThanks for the info. It makes sense in that case. Though the JVM can be very performant when written properly, and especially now with ZGC, Valhalla, Panama, etc.
- agallego 6y agoah yeah no doubt. I've read the recent gc code in the jvm tree. it's beautiful. We just had a ton years of experience with c++ and it was a good fit for seastar.io - this all came from me messing around with https://github.com/smfrpc/smf https://github.com/smfrpc/smf and seeing what one could do w/ DMA (no kernel page cache)