talks

Log | Files | Refs

commit 3a742253aebdcccc944b17ffdc0d9d0672d16e48
parent 0f18d87c984b7ddb7dc3a7fbe05f2fff7de52c38
Author: dwrz <dwrz@dwrz.net>
Date:   Wed,  3 Jun 2020 03:08:39 +0000

Update concurrency slides

Diffstat:
Mconcurrency/slides.org | 10+++++++---
1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/concurrency/slides.org b/concurrency/slides.org @@ -2,7 +2,6 @@ - David Wen Riccardi-Zhu - Senior Software Engineer @ Good Uncle -- https://github.com/dwrz - dwrz@dwrz.net Slides and code: https://github.com/dwrz/talks/concurrency. @@ -136,6 +135,10 @@ Even before that, computers were able to multitask with one core. * 20. Single Core [[file:images/single-core-concurrency.jpg]] +#+begin_src bash +strace echo "hello world" +#+end_src + * 21. Multi Core [[file:images/preemptive-scheduling-multi-core.jpg]] @@ -299,6 +302,7 @@ Run: [[file:cmd/mutex/run.sh]] - Up to how the scheduler(s) order things at execution time. - Concealed bugs - Heisenbugs +- Deadlock and Livelock * 40. Message Passing @@ -359,7 +363,7 @@ Probably not, because: - Network load - CPU - Ranking goroutine becomes a chokepoint. - - Data structures and algorithms could help here. + - Better data structures and algorithms could help here. - Goroutines are cheap, but not free. * 49. Possible Solutions @@ -458,7 +462,7 @@ Concurrent applications running concurrently on distributed computers. - Provide context to help you understand what's going on. - Practical exposure, to expose some of the trade-offs. -- Awareness and Sensitivity +- Awareness and Intuition - Remember: - /Premature optimization is the root of all evil/.