SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am currently using a warmup script to preload the pages of my sites. The warmup works well but about 2 minutes after it ran the search becomes slow again. I have refreshed the page with the developer dashboard enabled and I can see which part is slow but I have no idea how I can prevent this rendering step to slow down. I'm using SharePoint 2010.

Why does "ExecuteWcfOperation:" takes 24 seconds to execute ?

  • Activate web part connections (0.05 ms)
  • Panneau d'affinement CreateChildControls (24226.22 ms)
    • DataBinding DataFormWebPart (Panneau d'affinement) (24226.00 ms)
      • RefinementManager.GetRefinementXml() (24121.95 ms)
        • SharePointSearchRuntime::SendRequest (24117.62 ms)
          • SharePointSearchRuntime::GetQueryResult (24117.03 ms)
            • CreateChannelActingAsLoggedOnUser:Microsoft.Office.Server.Search.Administration.ISearchServiceApplication (24086.46 ms)
              • GetServiceSecurityToken (24086.19 ms)
                • CacheHandle (24085.90 ms)
                  • CreateChannelActingAsLoggedOnUser:Microsoft.SharePoint.Administration.Claims.ISPWindowsTokenCacheServiceContract (0.32 ms)
                    • GetServiceSecurityToken (0.04 ms)
                    • CreateChannelWithIssuedToken (0.15 ms)
                  • InitializeWcfOperation (0.02 ms)
                  • ExecuteWcfOperation: (24084.56 ms)
                    • CleanUpWcfOperation (0.01 ms)
              • CreateChannelWithIssuedToken (0.16 ms)
            • Execute (29.21 ms)
              • InitializeWcfOperation (0.03 ms)
              • ExecuteWcfOperation: /Execute (26.46 ms)
                • CleanUpWcfOperation (0.01 ms)
            • RecordQuery (0.08 ms)
              • EnqueueRecordQuery (0.02 ms)
          • SharePointSearchRuntime::MakeSharepointXmlResult (0.03 ms)
          • SharePointSearchRuntime::MakeSharepointXmlResult#1 (0.02 ms)
        • RefinementManager.GetRefinement(Dictionary<string, Dictionary<string, RefinementDataElement>>, XmlDocument, int) (1.52 ms)
  • Panneau d'affinement OnPreRender (2.85 ms)

share|improve this question
When you say "search becomes slow again" does that mean that it was fast right after the warm-up script? Does your warm-up script call search? I ask because many of the warm up scripts I've seen do not touch farm services like search, managed meta-data, or bcs. – Mike Oryszak Sep 6 '11 at 1:40
Yes, right after the warm-up the search is fast. I'm using this warm-up script PowerShell Warmup Script 2. In the extrasites file I added these links (I translated the Search folder from French so I'm not sure the path is good on an English based SP): http://.../Search, http://.../Search/Pages/default.aspx, http://.../Search/Pages/results.aspx, http://.../Search/Pages/results.aspx?k=a – rold2007 Sep 6 '11 at 21:23
what's the makeup of your farm? is the query service running on the web front end or on a seperate app server? – Tom Resing Sep 8 '11 at 15:08
This is my development server, everything is running on the same machine (SP + SQL Server). But my production environment has the same problem and SQL Server is installed on a separate machine for the production farm. – rold2007 Sep 8 '11 at 23:29
This sounds like it could be an authentication problem. Are you relying on an external domain controller? – SPDoctor Nov 5 '11 at 18:41

It could have something to do with CRL verification when you have a proxy or similar, from what I've experienced.

Add the following to your hosts file to "bypass" the CRL stuff:
share|improve this answer

Your Answer


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.