Post by account_disabled on Dec 7, 2023 3:25:46 GMT
For this purpose I modified the Program. Main method to the following form Concurrency in the application Additionally to allow the tool to read diagnostic data from the running process I modified the projects csproj file by adding the following XML fragment to the PropertyGroup elements Concurrency in the application After rebuilding the application I launched Visual Studio and selected the Launch New Process command from the Analyze Concurrency Visualizer menu.
In the parameters window I indicated the path to the exe file of my application Concurrency pitfalls After clicking the Start button my program was launched and then the data regarding the events recorded during its launch was loaded. Before carrying out this process it is Email Marketing List important to close all unnecessary applications so that their operation does not affect the analysis result. Additionally it is worth repeating this analysis several times to check whether the results are sufficiently close to each other and thus ensure the reliability of the results. For the purposes of this article I performed each analysis three times and comparing the results I found this number of repetitions to be sufficient. After loading finished I saw this graph Concurrency pitfalls It shows the degree of utilization of logical cores by the running application green during the analysis horizontal axis.
The degree of use of logical cores by other processes is presented in gray colors. White color represents unused CPU resources. From the point of view of this analysis however the more important data is hidden under the Threads element. After clicking it the following view appeared Concurrency pitfalls In this view at the top there is a bar that we already know from the Utilization view which here serves as a timeline. The area for which data is presented in the lower part is marked with a red frame limited by handles on the sides red squares.
In the parameters window I indicated the path to the exe file of my application Concurrency pitfalls After clicking the Start button my program was launched and then the data regarding the events recorded during its launch was loaded. Before carrying out this process it is Email Marketing List important to close all unnecessary applications so that their operation does not affect the analysis result. Additionally it is worth repeating this analysis several times to check whether the results are sufficiently close to each other and thus ensure the reliability of the results. For the purposes of this article I performed each analysis three times and comparing the results I found this number of repetitions to be sufficient. After loading finished I saw this graph Concurrency pitfalls It shows the degree of utilization of logical cores by the running application green during the analysis horizontal axis.
The degree of use of logical cores by other processes is presented in gray colors. White color represents unused CPU resources. From the point of view of this analysis however the more important data is hidden under the Threads element. After clicking it the following view appeared Concurrency pitfalls In this view at the top there is a bar that we already know from the Utilization view which here serves as a timeline. The area for which data is presented in the lower part is marked with a red frame limited by handles on the sides red squares.