I believe yes, there are. As this is the preview version there are possibilities for the memory leaks and other development issues. In the SharePoint 2013 server go to task manager and see what is taking more memory. You should see something like below.
We see the Name of the component which is taking huge memory is "Microsoft Office 2013 component". Yes, this is the reason for memory leaks. When you switched to process view you will find out what is that process. It is 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.
Solution:
We see the Name of the component which is taking huge memory is "Microsoft Office 2013 component". Yes, this is the reason for memory leaks. When you switched to process view you will find out what is that process. It is 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.
Solution:
- We can reduce the performance level of the search service by using the below powershell command.
- Set-SPEnterpriseSearchService -PerformanceLevel Reduced
- Open the file from the location C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config and find the line <noderunnersettings tag. We must set the attribute memoryLimitMegabytes value from 0 to some value which you should like to give. I have given 256, so that it will not grow too much that it should. The tag should look like below.
<nodeRunnerSettings memoryLimitMegabytes="256" />
No comments:
Post a Comment