Profiling Windows Services

Use this forum to discuss subjects that don't belong in the other forums.
Post Reply
Posts: 1
Joined: Tue Mar 22, 2005 1:54 pm

Profiling Windows Services

Post by beanmf » Tue Mar 22, 2005 2:14 pm

I have a multi-threaded .Net Window Service on a 4cpu server. App domains are involved. Some profilers won't touch this kind of problem. What can you do (or what can I do to trace memory problems)? I can exercise the service code locally on a single cpu machine, but that may not be quite the same.

Andreas Suurkuusk
Posts: 1030
Joined: Wed Mar 02, 2005 7:53 pm

Post by Andreas Suurkuusk » Tue Mar 22, 2005 3:04 pm

When AppDomains are involved, it is recommended that you disable root referee identification and heap utilization tracking (using the Settings form under the Tools menu).

If you disable those features, .NET Memory Profiler should be able to profile your service.

Are you experiencing a specific problem?
Best regards,

Andreas Suurkuusk
SciTech Software AB

Post Reply

Who is online

Users browsing this forum: No registered users and 8 guests