Profiling net.tcp

• 
  Thanks for your post. ANTS Profiler 3 is limited to one process at a time, so even if the service is hosted on the local machine, you can either profiler the WCF client or the service (presumably by profiling IIS), but not both together.

  Brian Donahue April 30, 2009 14:12

  - 0 +
• 
  i'm using Ants performance profiler 4.
  is it possible then to just profiling the tcp service?

  meir.rivkin May 03, 2009 04:29

  - 0 +
• 
  I don't see why not. If the service is on the local machine and the correct application type is chosen, you can profile it. Please let us know if you are running into a specific problem.

  Brian Donahue May 04, 2009 07:56

  - 0 +
• 
  Hello .
  
  This means that I can profile net.[url=tcp://..]tcp://..[/url]. ??

  alexyag February 23, 2012 10:32

  - 0 +
• 
  Yes. The only thing stopping you is the UI only allows you to enter http. So if you configure the web app to answer on both HTTP and TCP, you can invoke the webservice using either.

  Brian Donahue February 23, 2012 12:47

  - 0 +
• 
  So you tell me , that though my client-side app talks to wcf service over net.tcp , I only need to add an http endpoint on the service , and enter the address in the ANTS Profiler , and it will work ?
  
  Or I have to change my client-side app too ? Because that's a problem for me..
  
  Thanks .

  alexyag February 26, 2012 01:49

  - 0 +
• 
  You don't need to change anything else, provided you "profile on original port".

  Brian Donahue February 27, 2012 04:07

  - 0 +

Add comment

Please sign in to leave a comment.