07-23-2023, 12:40 AM
## Background ##
We are currently developing a web application, which relies on ASP .NET MVC 5, Angular.JS 1.4, Web API 2 and Entity Framework 6. For scalability reasons, the web application heavility relies on the async/await pattern. Our domain requires some cpu-intensive calculations, which can takes some seconds (<10s). In the past some team members used Task.Run, in order to speed up the calculations.Since starting an extra thread inside ASP .NET MVC or Web API controllers is considered a bad practise (the thread is not known by the IIS, so not considered on AppDomain Recycle => See [Stephen Cleary's blog post][1]), they used ConfigureAwait(false).
## Example ##
public async Task CalculateAsync(double param1, double param2)
{
// CalculateSync is synchronous and cpu-intensive (<10s)
await Task.Run(() => this.CalculateSync(param1, param2))).ConfigureAwait(false);
}
## Questions ##
- Is there any performance benefit in using Task.Run in an async Web API Controller for cpu-bound operations?
- Does ConfigureAwait(false) really avoid the creation of an extra thread?
[1]:
We are currently developing a web application, which relies on ASP .NET MVC 5, Angular.JS 1.4, Web API 2 and Entity Framework 6. For scalability reasons, the web application heavility relies on the async/await pattern. Our domain requires some cpu-intensive calculations, which can takes some seconds (<10s). In the past some team members used Task.Run, in order to speed up the calculations.Since starting an extra thread inside ASP .NET MVC or Web API controllers is considered a bad practise (the thread is not known by the IIS, so not considered on AppDomain Recycle => See [Stephen Cleary's blog post][1]), they used ConfigureAwait(false).
## Example ##
public async Task CalculateAsync(double param1, double param2)
{
// CalculateSync is synchronous and cpu-intensive (<10s)
await Task.Run(() => this.CalculateSync(param1, param2))).ConfigureAwait(false);
}
## Questions ##
- Is there any performance benefit in using Task.Run in an async Web API Controller for cpu-bound operations?
- Does ConfigureAwait(false) really avoid the creation of an extra thread?
[1]:
[To see links please register here]