Gravatar for

Question by swamcts, Jan 6, 2017 12:02 PM

Coveo for sitecore using high CPU

Hi , currently we are experiencing high cpu volume on delivery server.


  • Current Coveo for Sitecore version: 4.0.450.0
  • Current Sitecore version: 7.2.140526
  • Current CES: 7.0 x64 Build 8541.0
  • Coveo Search API: 8.0


  • 1 Master – is configured with 4 Mirrors. Each master and mirror installed in separate machine.
  • Coveo for Sitecore installed on Sitecore Authoring Server.

Issue: We are facing high CPU utilization in Sitecore delivery servers.

Need to find out the CPU utilization on Coveo for Sitecore for full indexing and incremental indexing. Is full indexing and incremental indexing will affect the CPU utilization of Sitecore delivery server? Please let me know the way to reduce the CPU utilization?

Thanks Swami

1 Reply
Gravatar for

Answer by Sébastien Belzile, Jan 6, 2017 12:44 PM


If you are properly configured and followed the scaling guide, the C4SC installed on your Sitecore delivery servers should not index anything (Indexing strategies should be disabled on CDs). Therefore the CPU utilization by Coveo on your Sitecore CDs during indexing should be very low. This applies to other search providers as well.

If you want actual numbers, you can proceed the same way you would do to profile any .NET application. Personally, I would attach a profiler such as dotTrace to the Sitecore process. Or you could try running the Sitecore Pipeline profiler. This usually gives a good idea of the weaknesses during indexing.

Gravatar for

Comment by swamcts, Jan 6, 2017 2:29 PM

Thanks for the response!

I have installed coveo for sitecore only on authoring server, so indexing should happen only on authoring server right, i didnt install anything on delivery server, why its CPU utilization is high on the delivery server? Please reply

Gravatar for

Comment by Sébastien Belzile, Jan 6, 2017 2:41 PM

Well, if you did not install Coveo for Sitecore, I think Coveo might not be using your CPU. Maybe you should try the Sitecore stack exchange.

Also, since Coveo is installed on your CM server, you should also install it on your CDs, otherwise your search pages + search queries might not work properly on your CDs. Read and apply Sitecore and Coveo for Sitecore scaling guides please.

Gravatar for

Comment by Sébastien Belzile, Jan 6, 2017 3:02 PM

I discussed your issue with my colleagues:

The HTMLContentInBodyWithRequestProcessor, the processor generating quickviews and getting the body of your documents will query your CDs.

This will increase your CPU usage. There are many ways to reduce this usage. One of them is using caching for your pages and components: .

Gravatar for

Comment by swamcts, Jan 11, 2017 1:35 PM

In scaling guide, it mentioned that we need to move coveo files from cm1 to cd1 server. i.e there will be file which has all coveo files, which needs to moved to delivery servers.

But am not able to find out the file.

I installed coveo for sitecore in authoring server, and many coveo files are created in one or more folders.

How to move the coveo files from CM1 to CD1?

What are the files we need to move?

Is entire website folder we need to move?

Coveo files availbale in authoring servers are ,

  • C:\inetpub\wwwroot\Sitecore\Website\App_Config\Include\Coveo
  • C:\inetpub\wwwroot\Sitecore\Website\Coveo
  • C:\inetpub\wwwroot\Sitecore\Website\bin - coveo dll files
  • C:\inetpub\wwwroot\Sitecore\Website\layouts\Coveo
  • etc..

please suggest.



Gravatar for

Comment by Sébastien Belzile, Jan 11, 2017 2:12 PM

The scaling guide says:

The Coveo for Sitecore package contains several files that are added to the Sitecore website directory. Those files must be copied to all Sitecore instances (CMs and CDs). The package contains a file.

To install Coveo for Sitecore, you have downloaded a .zip file from our website. This .zip is a Sitecore installation package. If you unzip it, you should see that it contains the a file. If you unzip this file, you will see that it contains all the files you need to copy.

I will adjust the documentation to make this more clear.

Ask a question