await Task.WhenAll(task1, task2); task1.Result; task2.Result about aspnetcorediagnosticscenarios HOT 10 CLOSED

Accessing .Result would be faster after the task has completed. awaiting the task is more idiomatic but results in a bigger state machine with more states (one for each await point in the method).
Look at the codegen here:

https://sharplab.io/#v2:EYLgtghgzgLgpgJwD4AEAMACFBGArAbgFgAoEgNwgQykTIEsBjODAXgwDs4B3DAZVsZwAFAEoipYhSoxoAa2ytqApgDoA4nBgBBKAE92DIQCIAFjBgAHEAHprXeyuB12AcxUMA9mCNjylDDJQsgBMijQI9Koa2noGxmaWNnYOLh4eLgA2cO5ePuIoAJxYAGwqAOomcOxaGRlCgfIANAFywb6S/ghwUACuGTAKbA3YKgBK3X0w+Bh+VF29/aFDrWMT/eIkKKH8EYIzxADeJBgnWADMJQA8OGgAfBjROvqGNxg9CBkirPcopQBiCC84wWMCE70+4gAvkA=

VS

https://sharplab.io/#v2:EYLgtghgzgLgpgJwD4AEAMACFBGArAbgFgAoEgNwgQykTIEsBjODAXgwDs4B3DAZVsZwAFAEoipYhSoxoAa2ytqApgDoA4nBgBBKAE92DIQCIAFjBgAHEAHprXeyuB12AcxUMA9mCNjylDDJQsgBMijQI9Koa2noGxmaWNnYOLh4eLgA2cO5ePuIoAJxYAGwqAOomcOxaGRlCgfIANAFywb6S/ghwUACuGTAKbIUtQdj4GH5UXb39oUNFDcHiJCih/BGCE8QA3iQY+1gAzCUAPDhoAHwY0Tr6hucYPQgZIqxXKKUAYgheAErdfRgQieL3EAF8gA=

from aspnetcorediagnosticscenarios.

I think another aspect to consider in picking one solution over the other is how do you want to handle exceptions, in particular on how you want to handle the scenario when only some tasks are failing.

from aspnetcorediagnosticscenarios.

Based on feedbacks, conclusion is that first version

var task1 = service.GetAsync1();
var task2 = service.GetAsync2();
await Task.WhenAll(task1, task2);
var result1 = task1.Result; 
var result2 = task2.Result;

have quite more performance than second version.

But second version

var task1 = service.GetAsync1();
var task2 = service.GetAsync2();
var result1 = await task1; 
var result2 = await task2;

is more idiomatic.

Thanks for precision, it's enough to restart debate with my coworkers.

from aspnetcorediagnosticscenarios.

I've always had this doubt
Regardless of the use of Result, the first of your codes could execute faster since Task.WhenAll could execute both Tasks in parallel.
I wonder if in this scenario the first code will be considered good practice 🤔
Maybe a modified version of the second one

var task1 = service.GetAsync1();
var task2 = service.GetAsync2();
await Task.WhenAll(task1, task2);
var result1 = await task1; 
var result2 = await task2;

It would be as fast as first due to Task.WhenAll and it is also avoiding Result (awaiting for the completed tasks should be immediate, but a little weird)

from aspnetcorediagnosticscenarios.

So @davidfowl, would would recommend the first version?

var task1 = service.GetAsync1();
var task2 = service.GetAsync2();
await Task.WhenAll(task1, task2);
var result1 = task1.Result; 
var result2 = task2.Result;

from aspnetcorediagnosticscenarios.

I've got enough feedback for me. Ticket can be close IMO.
But I see more concern raised by other people.

I let other people close this one, as some questions are pending. If there is no more activities several days, I'll close myself.

Thanks

from aspnetcorediagnosticscenarios.

A third version was introduced by @jjavierdguezas mid conversation and it isn't completely clear to me who is talking about which...

var task1 = service.GetAsync1();
var task2 = service.GetAsync2();
await Task.WhenAll(task1, task2);
var result1 = await task1; 
var result2 = await task2;

Does the await Task.WhenAll(task1, task2); improve or harm performance? @davidfowl uses this in his comparison. What if that line is omitted? Does it simplify the state machine denoted by @davidfowl ?

from aspnetcorediagnosticscenarios.

Wihout any update, I close this issue.
Thanks everyone

from aspnetcorediagnosticscenarios.

@andleer that's even more awaits 😄 so it's not as efficient.

from aspnetcorediagnosticscenarios.

@davidfowl agree that it is even more awaits but you used that scenario in your 2nd sharplap.io / codegen example. I realize it was most likely unintentional but I wonder if the inclusion impacts your comment earlier in this thread. Either way, I will take idiomatic over minimal performance differences. Thanks for all the contributions here!

from aspnetcorediagnosticscenarios.