Comments
7 comments
-
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.
-
i'm using Ants performance profiler 4.
is it possible then to just profiling the tcp service? -
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.
-
Hello .
This means that I can profile net.[url=tcp://..]tcp://..[/url]. ?? -
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.
-
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 . -
You don't need to change anything else, provided you "profile on original port".
Add comment
Please sign in to leave a comment.
i'm trying to profile net.tcp service which being used from wcf service.
scenario:
i've created wcf service which returns playlist xml according to given ID:
http://localhost/ExternalServices/Playl ... st?ID=1234
this service calls an internal net.tcp service which evalutes the request and gets the actual playlist from DB:
net.[url=tcp://localhost/Services/PlaylistManagerService.svc]tcp://localhost/Services/PlaylistManagerService.svc[/url]
however when running the profiler all i see is the external wcf service methods.
is it possible to profile the net.tcp service as well?
btw, i'm using Vista 64bit / win server 2008 sp1
-cheers