0

According to MSDN: https://msdn.microsoft.com/en-us/library/hh191443.aspx

"The async and await keywords don't cause additional threads to be created. Async methods don't require multithreading because an async method doesn't run on its own thread. The method runs on the current synchronization context and uses time on the thread only when the method is active. You can use Task.Run to move CPU-bound work to a background thread, but a background thread doesn't help with a process that's just waiting for results to become available."

So the .NET framework is not starting additional threads.

  1. What about the underlying OS?
  2. How are the blocking calls converted to non-blocking?
  3. What is the low level implementation?
f0rt
  • 1,801
  • 3
  • 17
  • 30
  • 2
    You ask way to many questions in one. The duplicate answers most of them I think. – Patrick Hofman Jul 22 '15 at 09:04
  • 1
    @f0rt: The OS does not use threads either. There are no blocking calls to convert. The lowest level of implementation uses DMA and interrupts. For more information, see my [There is no Thread](http://blog.stephencleary.com/2013/11/there-is-no-thread.html) blog post. – Stephen Cleary Jul 22 '15 at 12:23

0 Answers0