This commit is contained in:
@@ -728,4 +728,14 @@ JAVASCRIPT DOWNSAMPLING TOOL
|
||||
// if(ministats.Count>0){
|
||||
// var v=ministats.Count;
|
||||
// }
|
||||
// }
|
||||
// }
|
||||
|
||||
MEMORY LEAK DIAGNOSIS URLS
|
||||
https://docs.microsoft.com/en-us/dotnet/core/diagnostics/debug-memory-leak
|
||||
https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-counters
|
||||
https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-dump
|
||||
https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-trace
|
||||
|
||||
Might be doing GC Counts incorrectly, they don't sync up with the dotnet-counters tool which shows them drop back to zero regularly when I stop burn test
|
||||
https://michaelscodingspot.com/ways-to-cause-memory-leaks-in-dotnet/
|
||||
https://bennettadelson.wordpress.com/2013/04/11/using-perfview-to-diagnose-a-net-memory-leak-2/
|
||||
|
||||
Reference in New Issue
Block a user