Comments
Sort by recent activity
Okay, I figured the problem out. At startup, the application reads data from the hard drive - to speed this up, several Tasks are created for parallel reads. After all the Tasks are finished, their threads return to the threadpool. For some reason, these threads continue to be included into profiling results. J. / comments
Okay, I figured the problem out. At startup, the application reads data from the hard drive - to speed this up, several Tasks are created for parallel reads. After all the Tasks are finished, their...
Hello Peter, apologies, I should have made my query clearer. Yes, its exactly how you've put it. Another hint at the fact that the profiler is not showing the desired detail is the following look into the profiling results of Main - the 'get results' line is where the code spends 100% of its runtime yet the code inspector shows 0.000. [image] Thank you, J. / comments
Hello Peter, apologies, I should have made my query clearer. Yes, its exactly how you've put it. Another hint at the fact that the profiler is not showing the desired detail is the following look i...