Our IT team is trying to track down some memory issues we're having in production with a specific customer. Since this is a classic ASP application on Win2K3/IIS6 we've determined that DebugDiag/WinDbg are the best ways for us to take a memory dump and analyze it for root cause of the issue.
Since we can only get a TRUE representation of the issue on production, we want to generate a dump there, but in order to get the green light for ANY kind of tracing in production, we need to somehow calculate the overhead of running the tools (leaktracking dll).
If we can say "running this in production should only add 5% overhead to your system", its more likely we can proceed with our tests.
Any advice on the best way to determine this? Should we use PERFMON counters? If so, which counters would be useful?