The File Cache counters demonstrate whether you have enough memory for IIS:

Document Cache Hits – Total number of fruitful queries in the client mode record store since administration startup. The favored esteem relies upon substance. For instance, for static substance, the esteem ought to be high.

Record Cache Hits % – The proportion of client mode document reserve hits to add up to store demands (since administration startup). A low counter esteem (joined with a low Kernel: URI Cache Hits % esteem) could imply that you have to analyze why your documents are not being stored.

Document Cache Misses – Total number of ineffective queries in the client mode record reserve since administration startup.

Document Cache Flushes – The quantity of records expelled from the client mode reserve since administration startup.

URI reserve counters give execution measurements in regards to sites and web applications that may keep running on your server.

URI Cache Flushes – Counts the quantity of URI reserve flushes that have happened since the administration startup. Records are flushed if a reaction is taking longer than determined in the edge or if a document was altered or changed.

URI Cache Hits – Counts the quantity of fruitful queries in the URI store since the administration startup. A low an incentive for this counter is a solid sign that demands are not finding reserved reactions.

URI Cache Hits % – The proportion of URI Cache Hits to add up to reserve demands since administration startup.

URI Cache Misses – Total number of ineffective queries in the client mode URI reserve since administration startup. You should need to explore for issues if this esteem is high, in mix with a low URI Cache Hits esteem.

This TechNet article dives further into Web Service store counters.

Web Service

These counters give imperative data about the quantity of clients getting to the web administration and the volume of information traded.

Bytes got/sec – This counter demonstrates the rate that information is gotten by the Web administration.

Bytes sent/sec – This is the rate that information is sent by the Web administration.

Bytes all out/sec – The total of the two counters above. It shows the all out rate of bytes exchanged by the Web administration.

Association endeavors/sec: The rate that associations with the Web administration are endeavored.

Get Requests/sec – This is the rate of HTTP GET demands. High qualities show that your web server is over-burden.

Post Requests/sec – This is the rate HTTP POST demands. Once more, high qualities recommend the need to take measures.

Current Connections – number of current associations with the Web administration. This present counter's understanding relies on numerous factors, for example, the kind of solicitations (ISAPI, CGI, static HTML, and so on.), CPU use, and whatnot. So you'd have to do some examination to triage any fundamental issues.

Notwithstanding these counters, in the event that you are creating web applications with ASP.NET there are some valuable ASP.NET Performance Counters you should monitor, to guarantee smooth running of your applications and server.

For an increasingly itemized outline of Web Service counters look at this TechNet article.

Windows Tools

Windows OS comes furnished with some helpful devices you can use out of the case.

For more information, check Ghanatrvl.com