Comments
Sort by recent activity
Hello Jessica,
thank you for the info!
And no, it is not using a lot of unmanaged memory, so this is not needed.
Attaching to process seems to work nicely.
Actually, I haven't found any alternative product that can profile using net.tcp. So far ANTS is the best of the ones I tried.
But still new at hunting down memory problems, but ANTS sure makes it easier than using WinDbg atleast. [image]
Best regards,
R
jessica.ramos wrote:
Hi there,
Thanks for your post!
Regarding your query, there are two features that are not available when using "Attach to process": "Track disposal of IDisposable objects" and "Profile unmanaged memory allocations". If your code doesn't allocate much unmanaged memory and you're not concerned about IDisposable objects though, then attaching to process should provide enough information to analyze the memory usage of your WCF app.
Attaching to process is actually the better option when profiling net.tcp as the profiler doesn't officially support profiling non-http/https bindings, so sorry to say.
There have been a few other workarounds that have worked to profile net.tcp in the past, which is what were are already doing I believe: adding a dummy http binding to the site in IIS then to tell ANTS to profile it at the http:// address and not the net.tcp:// address, and then having your webservice client consume away at the normal net.tcp address. This unfortunately doesn't always work though--the profiler sometimes can't hook into the correct IIS process when starting it this way. (Another workaround was to create a console application to host the service which I know is not ideal.)
I hope attaching to process will be sufficient--please let me know how you get on! I've also created a feature request for profiling non-http/https protocols, MP-2327.
/ comments
Hello Jessica,
thank you for the info!
And no, it is not using a lot of unmanaged memory, so this is not needed.
Attaching to process seems to work nicely.
Actually, I haven't found any alternative...