How to Limit NodeRunner.exe High Memory, CPU Usage

roblem: NodeRunner.exe is consuming a lot of memory and CPU resulted in performance issues on SharePoint 2013 server.

Solution:
NodeRunner.exe is a SharePoint 2013 Search service component and it is resource hungry. To reduce the CPU and Memory impact of this process, follow below steps:

Step 1: Reduce the CPU impact of the search service
By default SharePoint search uses "maximum" to speed up its search crawling process. To reduce the CPU usage of the search service, run this PowerShell script from any one of your SharePoint 2013 server:

Set-SPEnterpriseSearchService -PerformanceLevel Reduced

This sets Search Service Application crawl component to use less number of threads.

Step 2: Limit the NodeRunner.exe‘s Memory usage:

  • Open the configuration file at "C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config"
  • Locate the node "nodeRunnerSettings", Set the value for "memoryLimitMegabytes" attribute to specific value (E.g. 1024). By default its value is 0 (which means unlimited memory). 

Step 3: Restart Search Service
For the above steps to take effect, You have to restart SharePoint 2013 search service. Go to Services console, restart SharePoint Search Host Controller process. Or use the PowerShell cmdlet to restart Search host controller process:

Restart-Service SPSearchHostController

The downside of the above changes: Since you are restricting resources to SharePoint search service, it increases search crawl time!

Do not limit node runner memory in Production Servers!Instead try increasing the Memory on SharePoint Production servers.

PowerShell to Set NodeRunner config:

#NodeRunner File Path
$NRFile= "C:\Program Files\Microsoft Office Servers\15.0\Search\Runtime\1.0\noderunner.exe.config"

#Get the XML
$NodeRunnerConfig = New-Object XML
$NodeRunnerConfig.Load($NRFile)

#Set Limit to 100 MB
$NodeRunnerConfig.configuration.nodeRunnerSettings.memoryLimitMegabytes = "100"
$NodeRunnerConfig.Save($NRFile)

#Read more: http://www.sharepointdiary.com/2015/02/limit-noderunner-high-memory-cpu-usage.html#ixzz5OhFQ8yKc

http://www.sharepointdiary.com/2015/02/limit-noderunner-high-memory-cpu-usage.html

原文地址:https://www.cnblogs.com/jianyus/p/9505272.html

时间: 2024-11-10 07:04:14

How to Limit NodeRunner.exe High Memory, CPU Usage的相关文章

Apache服务器httpd.exe进程占用cpu超过50%的解决方法

httpd.exe进程占用cpu超过50%,关闭掉Apache服务,cpu应用率立刻下降到0.  重新启动Apache又出现占用cpu高的情况.  原因是:httpd.exe和防火墙配置有冲突. 解决方法如下: 1.网上邻居->本地链接->属性->internet协议(TCP/IP)->属性->高级->wins标签->去掉起用LMhosts查询前的勾. 2.控制面版->windows防火墙->高级标签->本地链接设置->服务的标签里勾选安全

Yourkit 学习笔记-CPU Usage telemetry

1.CPU profiling 2015/5/5 19:09:51 1.1 CPU Usage telemetry(利用率) 在CPU下的CPU Usage telemetry菜单下可以显示当前CPU利用率 CPU性能模式包含了Sampling,tracing,call counting三种模式. 当开始监控应用服务器性能的时候,就可以通过CPU分析控制快速才按进行控制了: Sampling模式 定期查询stack中运行较慢的代码,没有方法调用数,CPU利用率. 采用sampling模式,对服务

【转载】解决mysqld-nt.exe大量占用CPU问题

服务器主机(Windows 2003 + IIS + PHP + MYSQL )近来 MySQL 服务进程 (mysqld-nt.exe) CPU 占用率总为 100% 高居不下.此主机有10个左右的 database, 分别给十个网站调用.据朋友测试,导致 mysqld-nt.exe cpu 占用奇高的是网站A,一旦在 IIS 中将此网站停止服务,CPU 占用就降下来了.一启用,则马上上升. MYSQL CPU 占用 100% 的解决过程 今天早上仔细检查了一下.目前此网站的七日平均日 IP

Getting Physical With Memory.CPU如何操作内存

原文标题:Getting Physical With Memory 原文地址:http://duartes.org/gustavo/blog/ [注:本人水平有限,只好挑一些国外高手的精彩文章翻译一下.一来自己复习,二来与大家分享.] 在你试图理解一个复杂的系统时,如果能揭去表面的抽象并专注于最低级别的概念,往往会有不小的收获.在这个精神的指导下,让我们看看对于内存和I/O端口操作来说最简单.最基础的概念,即CPU与总线之间的接口.其中的细节是很多上层概念的基础,比如线程同步.当然了,既然我是个

memory CPU cache books

http://www.amazon.com/Consistency-Coherence-Synthesis-Lectures-Architecture/dp/1608455645/ref=pd_sim_14_1?ie=UTF8&dpID=416Va%2B7GPIL&dpSrc=sims&preST=_AC_UL160_SR129%2C160_&refRID=0NSDDKF5MWV2FXY1QTVQ A Primer on Memory Consistency and Cac

HDD&Memory&CPU调度机制(I/O硬件性能瓶颈)

java读取进程cpu usage

原文链接 /* ------------------------------------------------------------------------- */ /* * An implementation of JNI methods in com.vladium.utils.SystemInformation * class. The author compiled it using Microsoft Visual C++ but the code * should be easy

How to debug the CPU usage 100

Read the following lists: http://improve.dk/debugging-in-production-part-1-analyzing-100-cpu-usage-using-windbg/ http://improve.dk/debugging-in-production-part-2-latent-race-condition-bugs/

kernel_task high cpu usage

# Find the model $ system_profiler -detailLevel mini | grep "Model Identifier:" Model Identifier: MacBookPro8,2 # Move and backup the file $ mkdir -p ~/backup $ cd /System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/ACPI_SMC_