If you can explain/elaborate in an answer it is welcome. Honestly I don't know much about the ValueTask class and I'm going to study it. "await ValueTask" version: 17 sec (50% CPU) "await ValueTask" version: 31 sec (100% CPU) I tried this directly in VS because I needed a nuget package (Release build) and these are the results: TEST on i7
#Task coach runs slow code
Is there any workaround which doesn't involve the refactoring of all the async-await chain of calls all around the code? (the code base is big and complicated)Īs suggested in a comment I tried to use ValueTask insted of Task and it seems to solve the issue. (the drop in CPU usage is sharper on the AMD but it's also present on the Intel) Why there is not always 100% CPU usage (or 50% taking into account the worse case for CPU hyperthreading), but there is a drop in CPU usage in the async-await version of the code? I understand there are hardware differences (maybe the Intel hyperthreading is better, etc), but this question is not about the hardware performance. TEST on AMD 32 cores 3,00 Ghz (windows server 2019 圆4):
#Task coach runs slow pro
I've run some benchmarks using the code above in linq pad both on my i7 machine and the AMD ThreadRipper and these are the results: TEST on i7 quad-core 3,67 Ghz (windows 10 pro 圆4): But I get some very bad result when I try to run the code on a AMD ThreadRipper machine we have in our office. I runs the simulations quite successfully on my i7 machine.
The async-await version of the code exemplifies the situation of my simulation code. SYNC VERSIONĭouble Calc(double a, double i) => a + Math.Sin(i) Īsync Task Calc(double a, double i) => a + Math.Sin(i) Dump() call and paste the code in a console application if you want to test it directly in visual studio. I tested the following code using LinqPad with compiler optimization turned on you can remove the. I undestand there is some overhead using async/await, but I also expect that there should be not a huge difference in performance given that an already-completed task is returned and there should be no actual waiting.īut making some tests I noticed a big drop in performance (expecially on some hardware). The values returned from the mock actually simulate every possible response from the network call that can be received in production environment.
The simulations doesn't perform any network call: a mock is used which returns a value using Task.FromResult(). I also need to run some simulations on the code the code gets called billions of times concurrently during the simulation.
The code uses async/await because it performs some network calls in production environment. I have some c# code that runs fine on a webserver.
0 kommentar(er)
