eG Help

A web site/web application on SharePoint typically constitutes numerous web pages. The performance of each of these pages is a key determinant of user experience with the web site/web application as a whole! Each web page in turn is made up of multiple web parts, So, when a web page slows down, more often than not, one/more web parts that constitute that web page will be responsible for the slowness! This is why, when users complain that a web site/web application is slow, administrators should first check whether/not the web parts used to build that web site/web application are taking too long to load, and if so, why. This is where the SPWebPartsTest test helps!

For each web site, this test reports the time taken by the web parts in that site to load. In the event of undue delay in web part loading, the test also points administrators to the probable cause of the delay - is it because of processing delays in the web part? Is it because the web parts took too long to generate service calls? Or is it owing to inefficient queries to the backend database? Detailed diagnosis of the test also leads you to the precise service calls and queries that could have contributed to the slowness.

For this test to run and report metrics, the following pre-requisites should be fulfilled:

Output of the test : One set of results for each web site containing web parts that process requests for a duration longer than the configured MAX ACCEPTABLE DURATION

Measurement	Description	Measurement Unit	Interpretation
Duration	Indicates the time taken by the web parts in this web site to load.	Secs	Compare the value of this measure across web sites to identify the slowest web site. Use the detailed diagnosis of this measure to know the details of requests that were processed slowly by the web parts in this web site.
CPU_Duration	Indicates the time spent by the web parts in this web site processing requests.	Secs	If the value of the Duration measure is abnormally high, then compare the value of this measure with that of the Total_SQL_duration and service_calls_duration measures to determine the accurate source of the slowness - is it because of processing delays in the web parts? Is it because the web parts took too long to generate service calls? Or is it owing to inefficient queries run by the web parts in the backend database?
SQL_queries	Indicates the number of queries executed by the web parts in this web site.	Number	Use the detailed diagnosis of this measure to know which queries were run and the duration of each query. This way, long running queries can be identified.
Total_SQL_duration	Indicates the total time taken by the web parts in this web site to run SQL queries.	Secs	If the value of the Duration measure is abnormally high, then compare the value of this measure with that of the CPU_Duration and service_calls_duration measures to determine the accurate source of the slowness - is it because of processing delays in the web parts? Is it because the web parts took too long to generate service calls? Or is it owing to inefficient queries run by the web parts? If queries are delaying web part operations, use the detailed diagnosis of the SQL queries measure to identify the long running / inefficient queries and then proceed to fine-tune them.
SPRequests	Indicates the number of requests to the web parts in this web site.	Number	The detailed diagnosis of this measure reveals the URLs of the SharePoint requests and the processing time of each request. Requests for which the web parts in a web site took too long to respond can be isolated in this manner.
Asserts	Indicates the number of asserts performed by the web parts in this web site.	Number
Service_calls	Indicates the number of service calls generated by the web parts in this web site.	Number	The detailed diagnosis of this measure reveals the exact service calls that were generated by the web parts and the duration of each service call. Slow service calls can thus be identified.
service_calls_duration	Indicates the total time taken by the web parts in this web site to generate service calls.	Secs	If the value of the Duration measure is abnormally high, then compare the value of this measure with that of the CPU_Duration and Total_SQL_duration measures to determine the accurate source of the slowness - is it because of processing delays in the web parts? Is it because the web parts took too long to generate service calls? Or is it owing to inefficient queries run by the web parts? If service calls are delaying web part operations, use the detailed diagnosis of the Service calls measure to identify those service calls that were taking too long to generate and execute.