Concurrent Map in Go vs Java: Yet Another Meaningless Benchmark
Today we're comparing Java's j.u.c.ConcurrentHashMap and Go's xsync.MapOf in a totally non-scientific, unfair benchmark. While most of such language performance comparisons are generally useless and harmful, the purpose of this exercise is a comparis...
puzpuzpuz.dev3 min read
Shai Almog
25 years ago I was lucky. I faced my debugging ignorance. It's a skill we don't learn at school. Hopefully I can help you reach a similar ep
Very interesting. What I would really like to know is how this scales to hundreds/thousands of threads. I suspect that with the current implementation Go will beat Java due to the limitations of system threads and with Loom we'll see Java turn that around.