Databases
StackOverflow2013
Postsdbo
POsharepoint 2010 exceptionally slow for first load
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POsharepoint 2010 exceptionally slow for first load
    text
    copied!<p>Iam have a load balanced windows authenticated sharepoint 2010 farm. </p> <p>I also have a similar setup on another farm. </p> <p>Now the issue is that on the first load page load performance issue. In fact both the Farms are slow for the first load. </p> <p>Farm1 takes only 15 seconds whereas my Farm2 takes 90+ seconds to render the same page.</p> <p>I agree that its normal to take 15 seconds during first load but 90+ seconds! That doesnt seem right!? Why does Farm2 take so much of time to load? </p> <p>After I perform an IISRESET, its the first page visit that is terribly slow. But after this first visit to the page it becomes normal. </p> <p>I copy paste here what I mean by it (taken from the developer dashboard enabled):</p> <pre><code> BeginRequestHandler (0.18 ms) PostAuthenticateRequestHandler (0.10 ms) PostResolveRequestCacheHandler (70266.36 ms) ExecuteOnChannel:GetProfileProperties (56800.21 ms) CreateChannelAsProcess:Microsoft.Office.Server.UserProfiles.IProfilePropertyService (56203.42 ms) GetProcessSecurityTokenForServiceContext (56196.01 ms) CreateChannelWithIssuedToken (6.68 ms) InitializeWcfOperation (0.09 ms) ExecuteWcfOperation:http://Microsoft.Office.Server.UserProfiles/GetProfileProperties (76.54 ms) CleanUpWcfOperation (0.02 ms) GetWebPartPageContent (4983.56 ms) GetFileAndMetaInfo (4974.71 ms) Proxy Channel call for Enterprise Metadata Service (1033.40 ms) CreateChannelAsProcess:Microsoft.SharePoint.Taxonomy.IMetadataWebServiceApplication (23.08 ms) </code></pre> <p>As you can see, the ExecuteOnChannel:GetProfileProperties is taking 60 seconds. What is it and why does it get called? Pls advice.</p> <p>Kind Regards,</p> <p>Jai</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload