SPC2011: How the SharePoint Dev Team Troubleshoots Performance and Reliability

Notes from the SharePoint Conference 2011
Session:  How the SharePoint Dev Team Troubleshoots Performance and Reliability

SPMonitoredScope

  • captures performance
  • have one outer monitored scope to identify code
  • wrap calls to external code in monitored scope
  • specify SQL & SPRequestCounter
  • do not use in a for loop (due to resources)

Developer Dashboard

  • Can include SPMonitored scopes (unless its for sandbox)
  • Includes header and trace information

Caveats to the Developer Dashboard

  • available to all site administrators
  • trace logs may contain sensitive information
  • Only for aspx – not with ajax, scripts, office rich clients requests

Usage database

  • IIS logs
  • timer job executions
  • event logs
  • SQL queries (blocking, deadlock)

Caveats to Usage database

  • 7 day retention default (can change)
  • failed requests wont appear
  • SQL is costly for usage
  • only works for single farm

SPDiagnostic Studio 2010

  • troubleshoot visually

Caveats to SPDiagnostic Studio 2010

  • built for internal
  • not ideal for monitoring
  • good for bug finding/exploration
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: