That part comes under debugging, and the tool used is called profiler. So before hosting in production, you need to bring it down for testing. In testing environment, run the program and attach a profiler (Visual Studio has profilers, which edition you have?), profiler will tell you almost everything
* CPU usage
* Memory consumption
* Network, disk usage etc.
That way, you will be able to get a full overview of what your service is doing, and where CPU or memory consumption is wrong. If Visual Studio does not provide enough information you can look for some third-party, and paid solutions. Google them. :-)
Mike Dos Zhang: Visual Studio Profile WCF project and look into the source code[
^]
How to get started with WCF Performance profiling - Stack Overflow[
^]