Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

We have two 'identical' SharePoint farms; one production and one test. Both consist of 4 VMs with identical specifications. An application server, 2 WFEs and a SQL server. Both environments run a single web application which has the same WSP installed. The test environment has been restored from a site collection backup of the production environment so the content in both environments is for all intents and purposes the same. I have checked the load on all servers in both farms and resource usage (memory, disk, processor, network) is consistent for matching servers across both farms.

We have a publishing page on a web in the site collection which has a single web part which renders a custom view of an item from a list in the parent web that contains around 8500 items. The item is retrieved using Linq2SharePoint by the integer Id assigned by SharePoint when the item is created. In the production environment the page consistently takes around 10 seconds longer to load than on the test environment.

All other pages have roughly the same load times across the two environments. Other pages which perform the same function, using the same web part, but in different sub webs in the site collection have roughly the same load times. The performance difference is very specific to this one location where the web part is used.

I think I know where the delay is happening but have no idea why or how to resolve it. Studying the ULS logs and the trace output for the page in the production environment I can see the following line (obviously the execution time varies slightly between requests but is more or less consistent)

Leaving Monitored Scope (EnsureListItemsData#1). Execution Time=11006.7259945049

In the test environment the execution time is around 700ms. This seems a clear candidate for the approximately 10 second performance difference.

My question then is what is going on here? What happens in this method? Why is it taking so much longer in seemingly 'identical' environments? What can I do to resolve the problem?

share|improve this question
    
do you resolve your issue? we faced with exact the same behavior... –  Kai Mar 18 at 20:02
    
No I never found the cause of this. We still see it intermittently and the location in the site collection varies. About the only suggestion I can make is to look for and eliminate any memory leaks in the page life cycle. –  robwilliams Mar 19 at 10:05
add comment

1 Answer

same issue is disccused over here

http://social.technet.microsoft.com/Forums/en-US/sharepoint2010programming/thread/089ff463-9454-4621-81fa-dac1761a9075

share|improve this answer
    
No it isn't. That's just the top Google search result for the title of my question, which I kind of thought to do myself. But thanks anyway. Out with Reflector it is then. –  robwilliams Oct 19 '12 at 7:06
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.