Is it still a bad idea on .net to turn on memory trending due to issue with microsoft for production and causes suspension. Is this still issue?
Bad idea for all .net or just older versions? If ok, what versions?
Solved! Go to Solution.
the only improvement that microsoft did in this regard is that since .NET 4.5 it is possible to turn the flag needed for memory dumps on & off at runtime.
this means that in dynatrace versions starting with 6.1 and .NET 4.5, if you have the memory dump settings set to "automatic" it will turn this flag on immediately before a memory dump and immediately off after a memory dump. this way it keeps the runtime suspension impact on the GC to a minimum during regular operation.
however, I'm pretty sure that the suspension time during a memory dump was not improved.