Skip Ribbon Commands
Skip to main content

Anders Rask on SharePoint


Anders Rask on SharePoint > Posts > Throttling performance of your SharePoint 2013 Enterprise Search Service on your dev box
January 15
Throttling performance of your SharePoint 2013 Enterprise Search Service on your dev box

​If you have set up a SharePoint 2013 farm, for example for your development box, chances are you have wondered where all that good RAM went, and why performance is so slow when you start to add service applications to your farm.

A check in Process Monitor reveals that a fair chunk of RAM is used by a number of processes called Noderunner.exe (Microsoft® SharePoint® Search Component). These are the components you configured when creating your Search Service Topology. If you did this in PowerShell you can decide which components should run on what server (eg. Analytics Processing or Admin component).

In beta these processes had a memory leak, and the "cure" was to limit the space used by changing noderunner.exe.config. This however is *not* supported, and not recommended, so don't do this on production environment! If your components run out of memory they will start acting very weird and/or crash. I even have managed to kill my farm beyond repair by setting the memory limit too low, so consider yourself warned!

Another option for your dev farm is to change your performance level of your search service using

Set-SPEnterpriseSearchService -PerformanceLevel Reduced

This will reduce the maximum numbers of threads to the number of available processors. Note that this will only have effect on the server instance running the crawl component.

For more information on this topic read "Scale search for performance and availability in SharePoint Server 2013" on TechNet and the guide "Enterprise search architectures for SharePoint Server 2013".


Good post about SharPoint Search

I enjoyed your short but good post about SharePoint Search Performance. I even recommend this in production if your SharePoint Server has limited ram.
Check out my blog, not as adequate as yours.
 on 8/10/2015 9:22 AM

nice one

This is the question which I usually want to ask the query which I carry mostly are versatile and must be listened thoroughly I have been being asked several times about many different occasion to which I have definite answer to it
 on 7/10/2018 12:24 AM

SharePoint 13

These are the segments you arranged while making your Search Service Topology. so don't do this on generation condition! In the event that your parts come up short on memory they will begin acting extremely abnormal and additionally crash. I even have figured out how to execute my homestead hopeless by setting as far as possible too low, so view yourself as cautioned
 on 8/3/2018 2:06 AM

Add Comment


Body *

Migrated Source URL

Commentator Name

Commentator Email

BotCheck *

Are you human? What is the sum of fifty-two minus ten?