CODEWITHSUNDEEP
wcfperformanceiisperformancecounter
alex
alex

Reputation: 755

Webservice wcf performance counters for queue

Am trying to performance test a wcf webservice which should get a lot of traffic. Which performance counters are sensible to use and for which purpose..Naturally I am looking at CPU and RAM, but I would like to know when IIS is queing and when its having trouble...

Any advice on sensible performance counters gratefully received...

Cheers alex

Upvotes: 3

Views: 2808

Answers (3)

SASS_Shooter
SASS_Shooter

Reputation: 2216

Before you run your performance monitors, you want to add the registry key:

HKLM/Services/CurrentControlSet/service/
  Add ServiceModelService 4.0.0.0
  under that add Performance then add a DWORD FileMappingFile.
  The size for that will be number of services exposed * 33 * 350.

In your config you would then add

<system.ServiceModel>
  <diagnostics performanceCounters="ServiceOnly"/>
</system.ServiceModel>

You can watch the following counters: CPU / RAM (for memory leaks) / for each service Call and Call Duration as well as Calls Outstanding

CPU will show you how heavily your are saturating your server
RAM will show if you have memory leaks if it continues to grow and grow and grow
Calls will show the number of calls you are getting accumulative, 
Calls Per Second will give you the volume you're handling
Calls Outstanding are clients that are waiting because your services could not handle the volume.

If you find some questionable numbers in these groupings then start looking at other elements like Calls Faulted or Calls Failed. (not sure of the difference between a failure and a fault)

It is rare that you would need to dig further into the issues than what the service only numbers will provide. When you get into the other two sets of counters your shared memory utilization gets really high.

Upvotes: 0

Nat
Nat

Reputation: 14295

Analysing performance counters is complicated and takes a lot of practice, which is my way of saying that I am not experienced enough to give a complete list.

You are going to look for some specific things to start with. First off is of course how long it takes to return the webservice calls. This tells you if you even have a performance issue at that load. Next every one looks at CPU. This really does not tell you a lot however. RAM is good, but you want to know how often your app is paging to disk, so check the Page Faults/sec. Check your logical and physical disks for Current Disk Queue Length. If your physical disk is queing at all, you are reading/writing to much to the disk.

Beyond that you would normally be trying to find a specific and likely obscure problem.

I usually take performance testing in stages. Do a first test with the basics and if a particular page is having a problem look at the load it is causing.

If the whole production server is not performing adequately, it is easier to add more hardware, but I prefer looking at the code that is running and make that better.

Upvotes: 0

casperOne
casperOne

Reputation: 74530

MSDN has an entire section on WCF administration and diagnostics, and specifically, for performance counters in WCF.

There are also specific sections for performance counters hosted service calls, as well as for the endpoint and for operations.

I would suggest looking through those first, as there is a good amount of valuable information there.

Upvotes: 2

Related Questions