This commit is contained in:
@@ -763,4 +763,20 @@ https://bennettadelson.wordpress.com/2013/04/11/using-perfview-to-diagnose-a-net
|
||||
HOW TO SEE WHO CALLED A METHOD DURING RUNTIME
|
||||
keywords: caller, call method stack trace stacktrace
|
||||
//System.Diagnostics.Debug.WriteLine((new System.Diagnostics.StackTrace()).GetFrame(1).GetMethod().Name);
|
||||
//System.Diagnostics.Debug.WriteLine((new System.Diagnostics.StackTrace()).ToString().Substring(56,80));
|
||||
//System.Diagnostics.Debug.WriteLine((new System.Diagnostics.StackTrace()).ToString().Substring(56,80));
|
||||
|
||||
Profiling / perf testing / performance testing
|
||||
How to peformance test
|
||||
|
||||
get process id for AyaNova
|
||||
C:\temp\xfer\perf>dotnet-trace ps
|
||||
12048 AyaNova C:\temp\xfer\v8test\win-x64\ayanova\AyaNova.exe
|
||||
|
||||
collect data with dotnet trace:
|
||||
dotnet-trace collect --process-id 12048 --format Speedscope
|
||||
|
||||
Use speedscope or built in to Chrome flame graph
|
||||
https://www.hanselman.com/blog/dotnettrace-for-net-core-tracing-in-perfview-speedscope-chromium-event-trace-profiling-flame-graphs-and-more
|
||||
|
||||
how to read a flame graph:
|
||||
https://www.brendangregg.com/FlameGraphs/cpuflamegraphs.html
|
||||
Reference in New Issue
Block a user