Top 10 most important performance counters for Windows and their recommended values

• PhysicalDisk/%idle time - should not be less than ~%60

• PhysicalDisk/Avg. Disk sec/Read should not be higher than ~20ms

• PhysicalDisk/Avg. Disk sec/Write should not be higher than ~20ms

• PhysicalDisk/Current disk queue length. should not be higher than 2

• Memory\Available Mbytes, minimum 10% of memory should be free and available

• \Memory\Pages/sec should not be higher than 1000

• Network Interface(*)\Bytes Total/sec

  • Less than 40% of the interface consumed = Healthy

  • 41%-64% of the interface consumed = Monitor or Caution

  • 65-100% of the interface consumed = Critical, performance will be adversely affected

• Network Interface(*)\Output Queue Length

  • 0 = Healthy

  • 1-2 = Monitor or Caution

  • Greater than 2 = Critical, performance will be adversely affected

• Hyper-V Hypervisor Logical Processor(_Total)\% Total Run Time

  • Less than 60% consumed = Healthy

  • 60% - 89% consumed = Monitor or Caution

  • 90% - 100% consumed = Critical, performance will be adversely affected

• Paging File\%Usage should not be higher than %10

Comments

• Anonymous
  March 17, 2016
  Would you please describe how do you determine the recommended values?I want to use your recommended values as reference to configure alarms for custom metrics to monitor an amazon EC2 instance of windows server 2012 R2.ThanksKibria
  • Anonymous
    April 08, 2016
    These are based on general experience. Mostly okay. You can verify them from other technet resources.
• Anonymous
  March 30, 2016
  Hello, thank you for information, it's very useful, but I can't find Logical Processor% Total Run Time(_Total) counter in my Windows Server 2012R2 (Hypervisor VM Ware vSphere). Any suggestions?
  • Anonymous
    April 08, 2016
    This is particular to HyperV. corrected blog.
• Anonymous
  November 25, 2016
  can you suggest some performance counter for SQL and IIS