3 ms·
Concurrency does not equal parallelism. Lets say there's one core, or "hardware thread". Then the scheduler has no choice but to stick them all on the same thr
by caspervonb 8y ago
Concurrency does not equal parallelism.
Lets say there's one core, or "hardware thread". Then the scheduler has no choice but to stick them all on the same thread. They are running concurrently but not in parallel.
With more cores, Go can schedule them to run in parallel.
Rob Pike has a great talk on YouTube titled something like "Concurrency is not parallelism" on this exact thing.
- dpflan 8y agoIndeed, taken from "Go Proverbs" - https://go-proverbs.github.io/ https://go-proverbs.github.io/ "Concurrency is not parallelism." > Video: https://www.youtube.com/watch?v=PAAkCSZUG1c&t=3m42s https://www.youtube.com/watch?v=PAAkCSZUG1c&t=3m42s