SP2013 memory usage noderunner process

This blog article is based on the SharePoint 2013 preview. Be aware that things might work differently.

My colleague was recently configuring MMS on our SP2013 website farm and got some errors that indicated that memory was too low on the SharePoint server.

Error message:
Memory gates checking failed because the free memory (… bytes) is less than 5% of total memory. As a result, the service will not be available for incoming requests. To resolve this, either reduce the load on the machine or adjust the value of minFreeMemoryPercentageToActivateService on the serviceHostingEnvironment config element.

If you look at the server into the Task Manager you will see that the noderunner.exe processes will consume a lot of memory. These processes run for the search.

To free some memory you can restart the process “SharePoint Search Host Controller”. Don’t be afraid when restarting take some time, couple of minutes. A lot of memory must be freed.

noderun03

On our server we saw a 70% drop in memory usage. Configuring MMS was possible now.

noderun01

UPDATE 30/07/2012:
Read Corey Roth’s blog for more indepth info about the various noderunner processes.

There are 6 comments for this article
  1. Pingback: The requested service, ‘http://myserver:32843/guid/AppMng.svc’ could not be activated « Sharepoint 2010 and Sharepoint 2013 Blog
  2. Pingback: Configuring Access Services 2013 on Premises | MSDN Blogs
  3. Pingback: Configuring Access Services 2013 on Premises - Kirk Evans Blog - Site Home - MSDN Blogs
  4. Pingback: Enterprise Portal Installation fails due not enough memory | ErpCoder

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">