Async in C# - The Good, the Bad and the Ugly
- 1. Async in C# The good, the bad and the ugly 😋😒😭
- 2. Hi, I’m Stu ◍ F# |> I ❤ ◍ Developer at ◍ 8 years of experience in .NET ◍ Organiser of Bristol F# meetup and DDD South West ◍ Passionate about Open Source You can find me at @stuartblang
- 3. Sponsors
- 5. History of Async Async/Await introduced .NET 4.5 C# 5 2011 Async CTP 2010 You are here! 2017
- 6. “ It really troubles me how much async, bad async, really bad async we see in the wild Kathleen Dollard - .NET Rocks! #1143
- 8. The Good ◍Non-blocking waiting ◍There is no thread!
- 9. The Bad ◍Not clear what is true async ◍Performance overhead ◍Duplicated code ◍Async can’t go everywhere ◍Risk of async deadlocks ◍Doing it wrong is much worse that not doing it at all
- 10. How does it work? Compiler generated code
- 11. How does it work?
- 12. Synchronization Context What’s that about?
- 13. How does it work?
- 14. Continuing on Captured Context
- 16. Synchronization Context Cont. WindowsFormsSynchronizationContext DispatcherSynchronizationContext Default (ThreadPool) SynchronizationContext AspNetSynchronizationContext
- 17. SynchronizationContext Behaviors Specific Thread Used to Execute Delegates Exclusive (Delegates Execute One at a Time) Ordered (Delegates Execute in Queue Order) Send May Invoke Delegate Directly Post May Invoke Delegate Directly WinForms Yes Yes Yes If called from UI thread Never WPF Yes Yes Yes If called from UI thread Never Default No No No Always Never ASP.NET No Yes No Always Always
- 18. Deadlock
- 20. KA-BLAMO!
- 23. KA-BLAMO!
- 26. ContextFreeTask
- 27. vs-threading
- 28. Formal definition of async deadlocks You are susceptible to deadlocks if: 1. You have a current SynchronizationContext that enforces exclusive access; 2. Some code further into your call stack has access to it and can/does: a. Synchronously block on some async code; b. Within that async code awaits an incomplete task that does not use .ConfigureAwait(false), or temporarily removes the context. If you use .Result, .Wait(), .GetAwaiter().GetResult() you have done a dangerous thing, and you should be prepared to guard against naughty awaiters (you may not even control).
- 29. Resources Automated Tools ◍ Microsoft's AsyncPackage (Roslyn Analyzer) - Async006 - Detects more blocking calls than you can shake a stick at. ◍ ConfigureAwait.Fody (yuk) ◍ ConfigureAwait Checker for ReSharper ◍ ConfigureAwaitChecker - Roslyn Analyzer + VSIX ◍ DeadlockDetection Prevention Methods ◍ .ConfigureAwait(false) all the things ◍ ContextFreeTask ◍ Comment the code ◍ null the SynchronizationContext (with handy helper functions) ◍ async top to bottom (replace our libraries and framework where we have to) ◍ Deadlock detection in QA & Prod ◍ Detect deadlocks in unit tests? ◍ Use ASP.NET Core!
- 30. Awesome async resources ◍Stephen Cleary ◌ https://blog.stephencleary.com/ ◍Anthony Steele ◌ Avoiding basic mistakes in async await ◌ Resynchronising async code
- 31. Thanks!Any questions? You can find me at @stuartblang & stuart.b.lang@gmail.com 👍