Performing Asynchronous I/O Bound Operations (Jeffrey Richter)

In this talk, Jeff shows how to use C# 5's new async/await features (which he helped design with Microsoft). These features allow you to build scalable and responsive applications. We'll discuss how the compiler transforms your code, error handling, limitations, performance, and various other features to simplify your code while getting the most out of the underlying hardware.

[@spsmith1965]

Many years ago I worked at a company that sold a FTP-like application for mainframe datacenters. It ran on all popular versions of *nix and Windows. The Windows app was the slowest and used the most CPU. I refactored the Windows app to use async IO, overlapped IO and IO competition ports. After the refactor, the Windows app became the best performing (could completely saturated the network), and had the lowest CPU usage (almost undetectable). I was shocked. It was amazing. These technologies are the most amazing and most underappreciated APIs in Windows.

[@sach2372]

40:56 Elevator pitch Async await allow you to have sequential programming model, for writing code that performs I/O operations without blocking any threads, thereby allowing you to create more responsive and scalable software.

[@Chiramisudo]

It really bothers me when tech talks are uploaded at anything less than 720p at a minimum. This is half as many pixels. Does not look great on my 4k monitor. 😣 Even so, content-wise, excellent. Thanks for posting!

[@alekomrisxane]

This was fantastic explanation!!!

[@Nitishkatare]

This videos explained the Async/Await in details

[@leahnjr]

Excellent

[@aqshinn]

Excellent!

[@puyadaravi3109]

13:30 What does it mean for a DLL (which is a file) to be notified?

[@HandE2Go]

A DLL is required to have a function called DllMain, which takes a DWORD parameter called dwReason (u can call it whatever u want).. when a dll is loaded (Loadlibrary), the Dllmain function is called first with dwReason == DLL_PROCESS_ATTACH. when unloaded (edit: with FreeLibrary), it's called with DLL_PROCESS_DETACH. the dll author will put some init code in the process_attach case and cleanup code in the detach case.

[@puyadaravi3109]

@@HandE2Go Thank you for the explanation! :) It seems that the notification mentioned at 13:30 happens after the DLL is already loaded. So, is there another function for handling notifications? Edit: it seems the notification handlers are called DLL_THREAD_ATTACH and DLL_THREAD_DETACH

[@r1jsheth]

Brilliant.

[@focl2003]

Great!

[@uttamsuthar9940]

Really awesome... Must watch for programmer

[@garryiglesias4074]

I stand corrected, I was going to recommend it to my gardener friend. Thank you.

[@francistchatchoua2308]

Brillant

[@douggale5962]

Threads are only atrocious crap on Windows. On every other OS, creating a thread is nearly zero cost.