|
You are here |
morsmachine.dk | ||
| | | | |
swiftrocks.com
|
|
| | | | | Multithreading in general is a difficult thing to fully understand, but understanding how the CPU deals with concurrency is the key to writing good, fast code that does what you expected it to do. Otherwise, you might be abusing your user's CPUs but thinking everything is fine because they are too fast for you to notice that something is wrong. | |
| | | | |
www.ardanlabs.com
|
|
| | | | | Prelude This is the second post in a three part series that will provide an understanding of the mechanics and semantics behind the scheduler in Go. This post focuses on the Go scheduler. Index of the three part series: Scheduling In Go : Part I - OS Scheduler Scheduling In Go : Part II - Go Scheduler Scheduling In Go : Part III - Concurrency Introduction In the first part of this scheduling series, I explained aspects of the operating-system scheduler that I believe are important in understanding and ap... | |
| | | | |
kristoff.it
|
|
| | | | | Yes I know about that one talk from Rob Pike. | |
| | | | |
danluu.com
|
|
| | | [AI summary] The article discusses the evolution of CPU architecture and optimization techniques, emphasizing that modern CPUs have many features that developers can leverage without needing to understand low-level details. Key points include the importance of predictable code, memory locality, and the role of libraries and compilers in handling low-level optimizations. It also covers trends like hardware acceleration, custom chips, and the increasing complexity of modern CPUs, which introduces new challenges and opportunities. The article concludes by suggesting further reading and resources for deeper understanding. | ||