Performance Monitoring

Performance Monitoring

Performance Monitoring Strategy

  • Log Performance Objects that contain critical counters
  • Set logging interval to 15 minutes and log data over multiple weeks
  • Use Performance Monitor to display logged data for critical counters
  • Use the remaining counters to investigate the critical counters that show signs of a potential problem
    • Creeping increases in resource consumption over prolonged periods are signs of a leak
    • High resource consumption for prolonged periods with a related queue length above 2 are signs of a bottleneck
    • High ranges for non-optimum metrics, such as errors, cache misses, etc. are signs of a code or configuration issue

Steps for Monitoring Performance Counters

  • Run the Performance Monitor application
  • Right-click 'Performance > Data Collector Sets > User Defined' and select 'New > Data Collector Set'
  • Type a name and click 'Create Manually (Advanced)'
  • Add a checkmark to 'Create Data Logs > Performance Counter' and then click Next
  • Add the Performance Objects that contain the critical counters
  • Set interval for 15 minutes and click Next
  • Accept the default file system path %systemdrive%\PerfLogs\Admin\Sitecore and click Next
  • Select 'Start this data collector set now' and click Finish

ASP.NET Objects that contain Critical Performance Counters

  • .NET CLR Exceptions (_Global)
  • .NET CLR Memory (_Global) 
  • ASP.NET (*)
  • ASP.NET Applications (_Total)

IIS Objects that contain Critical Performance Counters

  • Web Service (_Total)
  • Web Service Cache (*)

Sitecore Objects that contain Critical Performance Counters

  • Sitecore.Caching (*)
  • Sitecore.Data (*)

SQL Objects that contain Critical Performance Counters

  • MSSQL.AccessMethods (*)
  • MSSQL.Buffer Manager (*)

System Objects that contain Critical Performance Counters

  • Memory (*)
  • Network Inferface (*)
  • Paging File (*)
  • Physical Disk (*)
  • Process (w3wp)
  • Processor (_Total)
  • System (*)

Sources