Kunal, We can definitely help you slow down NiFi. It is admittedly a bit high strung out of the box. There are several areas where you can tune it to calm down a bit. This includes things like processor scheduling, bored yield duration in nifi.properties, and so on.
Tuning for CPU without discussing other performance criteria will leave a lot left to discuss. What sort of throughput are you anticipating? Thanks On Tue, May 2, 2017 at 7:32 AM, Andrew Grande <[email protected]> wrote: > What is your flow doing? It very much depends on this. While 6 cores is not > a great hardware to run a full NiFi system on, I'd guess ReplaceText and > EvaluateJsonPath are the hotspots. See how much data queues up in front of > these processors. > > Andrew > > > On Tue, May 2, 2017, 5:09 AM kunal <[email protected]> wrote: >> >> Hi All, >> >> As we are using nifi for the restfull API development purpose and using >> mostly below components. >> HttpRequestHandler >> HttpResponseHandler >> Route on attribute >> ReplaceText >> ExecuteSQL >> PutSQL >> EvaluateJsonPath >> InvokeHttp >> etc >> After development we notice that the CPU utilisation is very high it >> almost >> taking 300% CPU utilisation on the 6 core processor with Average above 3 >> after changing the run scheduler on HttpRequestHandler as 1 from 0 it >> reduces to 160-190 >> which is also very high, also there is no abnormal behaviour found in the >> nifi logs. >> Please suggest how to resolve this issue >> >> >> >> >> -- >> View this message in context: >> http://apache-nifi-users-list.2361937.n4.nabble.com/Apache-nifi-1-0-0-consuming-high-CPU-utilization-tp1770.html >> Sent from the Apache NiFi Users List mailing list archive at Nabble.com.
