Is Task.Run considered bad practice in an ASP .NET MVC Web Application?

by

Is there any performance benefit in using Task.Run in an async Web API Controller for cpu-bound operations?

Zero. None. In fact, you’re hindering performance by spawning a new thread. Within the context of a web application, spawning a thread is not the same thing as running in the “background”. This is due to the nature of a web request. When there’s an incoming request, a thread is taken from the pool to service the request. Using async allows the thread to be returned before the end of the request, if and only if the thread is in a wait-state, i.e. idle. Spawning a thread to do work on, effectively idles the primary thread, allowing it to be returned to the pool, but you’ve still got an active thread. Returning the original thread to the pool does nothing at that point. Then, when the new thread finishes its work, you’ve got to request a main thread back from the pool, and finally return the response. The response cannot be returned until all work has completed, so whether you use 1 thread or a hundred, async or sync, the response cannot be returned until everything finishes. Therefore, using additional threads does nothing but add overhead.

Does ConfigureAwait(false) really avoid the creation of an extra thread?

No, or more appropriately, it’s not about that. ConfigureAwait is just an optimization hint, and only determines whether the original context is maintained between thread jumps. Long and short, it has nothing to do with the creation of a thread, and at least in the context of an ASP.NET application, has negligible performance impact either way.

More Related Contents:

  1. Calling async method synchronously
  2. How to use non-thread-safe async/await APIs and patterns with ASP.NET Web API?
  3. Nesting await in Parallel.ForEach [duplicate]
  4. Best practice to call ConfigureAwait for all server-side code
  5. Running multiple async tasks and waiting for them all to complete
  6. Parallel.ForEach and async-await [duplicate]
  7. Regarding usage of Task.Start() , Task.Run() and Task.Factory.StartNew()
  8. How to get the public IP address of a user in C#
  9. Could not find a part of the path … bin\roslyn\csc.exe
  10. Why Interface Layer/Abstract classes required in our project? [closed]
  11. Difference between await and ContinueWith
  12. Displaying standard DataTables in MVC
  13. Waiting for async/await inside a task
  14. Revisiting Task.ConfigureAwait(continueOnCapturedContext: false)
  15. ASP.Net MVC route to catch all *.aspx requests
  16. How to create roles in ASP.NET Core and assign them to users?
  17. Write PDF stream to response stream
  18. multiple awaits vs Task.WaitAll – equivalent?
  19. Using async without await?
  20. Executing tasks in parallel
  21. Difference between returning and awaiting a Task in an async method [duplicate]
  22. Use Task.Run() in synchronous method to avoid deadlock waiting on async method?
  23. A pattern for self-cancelling and restarting task
  24. SynchronizationLockException on Monitor.Exit when using await
  25. MEF with MVC 4 or 5 – Pluggable Architecture (2014)
  26. Redirect to another page when user is not authorized in asp.net mvc3
  27. How do you post a JSON file to an ASP.NET MVC Action?
  28. {version} wildcard in MVC4 Bundle
  29. ASP.NET – AppDomain.CurrentDomain.GetAssemblies() – Assemblies missing after AppDomain restart
  30. Opposite of [compare(” “)] data annotation in .net?

Leave a Comment