I've performance issues with my new SharePoint 2013 development environment.
When i checked memory usage in task manager then i have seen 5 microsoft office 2013 components taking more memory.
What are these Microsoft Office 2013 components and why are they consuming so much memory?
Switching to the details tab, these Microsoft Office 2013 components show up as noderunner.exe
As far as I know this is related to the search service process with new name. Even though our farm is new with very less data the noderunner processes are running and taking huge amount of memory. After good amount of research and read I have found the fix in the technet article here.
To apply the fix from this article on the SharePoint 2013 server start the SharePoint 2013 Management Shell and and enter the following command:
Set-SPEnterpriseSearchService –PerformanceLevel Reduced
Modify the C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config so that it can only consume X amount of RAM.
C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config
Edit this file, and locate the line <nodeRunnerSettings memoryLimitMegabytes="0" />
Provide a memory limit for the noderunner process, I set the limit at 150 as shown below.
After making these changes I recommend you restart your server. Although I have had no problem with just killing the noderunner.exe processes in Task Manager; SharePoint creates them again almost immediately.
Here reference.
When i checked memory usage in task manager then i have seen 5 microsoft office 2013 components taking more memory.
What are these Microsoft Office 2013 components and why are they consuming so much memory?
Switching to the details tab, these Microsoft Office 2013 components show up as noderunner.exe
As far as I know this is related to the search service process with new name. Even though our farm is new with very less data the noderunner processes are running and taking huge amount of memory. After good amount of research and read I have found the fix in the technet article here.
To apply the fix from this article on the SharePoint 2013 server start the SharePoint 2013 Management Shell and and enter the following command:
Set-SPEnterpriseSearchService –PerformanceLevel Reduced
Modify the C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config so that it can only consume X amount of RAM.
C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config
Edit this file, and locate the line <nodeRunnerSettings memoryLimitMegabytes="0" />
Provide a memory limit for the noderunner process, I set the limit at 150 as shown below.
After making these changes I recommend you restart your server. Although I have had no problem with just killing the noderunner.exe processes in Task Manager; SharePoint creates them again almost immediately.
Here reference.