# Scheduling In Go : Part III - Concurrency

DevFeed: [Scheduling In Go : Part III - Concurrency](<https://devfeed.tech/articles/scheduling-in-go-part-iii-concurrency-22142.md>)

Original publisher: [Read original article](<https://www.ardanlabs.com/blog/2018/12/scheduling-in-go-part3.html>)

Published: 2025-05-12T00:00:00Z

Content type: tutorial

Language: en

Sources: [William Kennedy](<https://devfeed.tech/sources/william-kennedy.md>)

Topics: [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [Go Language](<https://devfeed.tech/topics/go-language.md>), [benchmarking](<https://devfeed.tech/topics/benchmarking.md>), [IO](<https://devfeed.tech/topics/io.md>), [Sorting](<https://devfeed.tech/topics/sorting.md>)

Tags: [ardan-labs](<https://devfeed.tech/tags/ardan-labs.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [blog](<https://devfeed.tech/tags/blog.md>), [concepts](<https://devfeed.tech/tags/concepts.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [go](<https://devfeed.tech/tags/go.md>), [go-programming](<https://devfeed.tech/tags/go-programming.md>), [golang](<https://devfeed.tech/tags/golang.md>), [io](<https://devfeed.tech/tags/io.md>), [parallelism](<https://devfeed.tech/tags/parallelism.md>), [performance](<https://devfeed.tech/tags/performance.md>), [programming](<https://devfeed.tech/tags/programming.md>), [sorting](<https://devfeed.tech/tags/sorting.md>), [technical](<https://devfeed.tech/tags/technical.md>)

## AI overview

This third post in a series about the Go scheduler explains concurrency as out-of-order execution and distinguishes it from parallelism. It discusses how CPU-bound and I/O-bound workloads affect the decision to use concurrency, using practical examples and benchmarks to show that parallelism can improve CPU-bound performance while concurrency alone can benefit I/O-bound work.

## Source excerpt

Although originally written in 2018, the following concepts remain essential for developers working with concurrency. This blogpost focuses on concurrency, distinguishing it from parallelism by defining it as "out of order" execution. It emphasizes the importance of understanding workload types--CPU bound (e.g., summing, sorting) and IO bound (e.g., file reading)--to assess when concurrency is appropriate. Through practical examples and benchmarks, it shows that parallelism boosts performance for CPU bound tasks, while concurrency alone benefits IO bound workloads. The post underscores that identifying workload type is key to applying concurrency effectively without added complexity.