4 ms·
This is timely as I'm troubleshooting a .NET app with randomly long garbage collection times. I'm just the sysadmin in this scenario, without access to the code
by mysterydip 10y ago
This is timely as I'm troubleshooting a .NET app with randomly long garbage collection times. I'm just the sysadmin in this scenario, without access to the code, so I'm approaching it from Splunk and AppDynamics. If anyone has suggestions beyond this article, I'd appreciate it :)
- ZenoArrow 10y agoThis may be of interest: http://www.red-gate.com/products/dotnet-development/ants-memory-profiler/learning-memory-management/memory-management-fundamentals http://www.red-gate.com/products/dotnet-development/ants-mem...
- prefect42 10y agoThat's a nice memory profiler, have good success with it. I've also used DebugDiag, https://www.microsoft.com/en-us/download/details.aspx?id=49924 https://www.microsoft.com/en-us/download/details.aspx?id=499... and plain ol' perfmon and its performance counters, to help track down GC-related issues.
- gumaflux 10y agoAgreed. Starting point PerfMon and PerfCounters, as an addition to great suggested profilers I would also have a look at PerfView / ETW. https://blogs.msdn.microsoft.com/dotnet/2012/10/09/improving-your-apps-performance-with-perfview/ https://blogs.msdn.microsoft.com/dotnet/2012/10/09/improving...