---
title: "Comment by Shai Almog on \"Concurrent Map in Go vs Java: Yet Another Meaningless Benchmark\" | Hashnode"
description: "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 b"
url: "https://hashnode.com/posts/concurrent-map-in-go-vs-java-yet-another-meaningless-benchmark/636562eef56b98b1f770a9b7/comment/6365dd455efad7ad599cb8be"
---

[Discussion](https://hashnode.com/posts/concurrent-map-in-go-vs-java-yet-another-meaningless-benchmark/636562eef56b98b1f770a9b7)

Comment [Concurrent Map in Go vs Java: Yet Another Meaningless Benchmark](https://hashnode.com/posts/concurrent-map-in-go-vs-java-yet-another-meaningless-benchmark/636562eef56b98b1f770a9b7)

[Shai Almog](https://hashnode.com/@codenameone)

[Nov 5, 2022](https://hashnode.com/posts/concurrent-map-in-go-vs-java-yet-another-meaningless-benchmark/636562eef56b98b1f770a9b7/comment/6365dd455efad7ad599cb8be)

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.

[Andrei Pechkurov](https://hashnode.com/@puzpuzpuz)

[Nov 5, 2022](https://hashnode.com/posts/concurrent-map-in-go-vs-java-yet-another-meaningless-benchmark/636562eef56b98b1f770a9b7/comment/6365dd455efad7ad599cb8be#reply-636607825efad7ad599cbbfd)

Read operations will scale only with increased CPU core count. As for writes, they might scale better in Go with increased number of goroutines as long as the hash table bucket count is large enough. That's because of cheaper context switches in green threads vs OS threads. Project Loom may indeed change that.