Your development team has discovered that a SharePoint 2010 application has performance issues. The
application is experiencing periodic application pool recycling due to memory thresholds being exceeded. You
need to determine the cause of this behavior.
Which logs should you tell your team to analyze?
A.
Analyze the IIS logs for entries related to SPPersistedObject objects.
B.
Analyze the IIS logs for entries related to SPRequest objects.
C.
Analyze the Unified Logging Service (ULS) logs for entries related to SPPersistedObject objects.
D.
Analyze the ULS logs for entries related to SPRequest objects.
http://msdn.microsoft.com/en-us/library/ee557362(v=office.14).aspx
In custom development, when SharePoint objects – implementing IDesposible don’t release memory, it may cause the following unusual behavior.
– SharePoint Foundation application pool recycling frequently
– Application crashes, the performance of heap corruption in the debugger
– Internet Information Services (IIS) worker process uses lots of memory
– poor performance of systems and applications
To determine whether the cause is a memory leak due to incorrectly disposed objects, check the ULS logs (available at C:\Program Files\Common Files\microsoft shared\Web Server Extensions\14\LOGS) for entries related to the SPRequest object.