mirror of
https://github.com/teivah/100-go-mistakes.git
synced 2026-06-22 01:17:11 +08:00
Adding link to concurrency faster post
This commit is contained in:
parent
d9bfd05729
commit
66b5298254
1 changed files with 1 additions and 1 deletions
|
|
@ -264,7 +264,7 @@ In many cases, you shouldn’t ignore an error returned by a `defer` function. E
|
|||
|
||||
Understanding the fundamental differences between concurrency and parallelism is a cornerstone of the Go developer’s knowledge. Concurrency is about structure, whereas parallelism is about execution.
|
||||
|
||||
#### Thinking concurrency is always faster (#56)
|
||||
#### [Thinking concurrency is always faster](https://teivah.medium.com/concurrency-isnt-always-faster-in-go-de325168907c) (#56)
|
||||
|
||||
To be a proficient developer, you must acknowledge that concurrency isn’t always faster. Solutions involving parallelization of minimal workloads may not necessarily be faster than a sequential implementation. Benchmarking sequential versus concurrent solutions should be the way to validate assumptions.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue