Hi Asmath,
In addition to excellent answers from Nathan and Jorge, I just want to add
that NiFi should be seen as a framework enabling you to build efficient
flows. But just like any framework and you can do pretty much anything you
want, it can be something good but it can also be something bad.
Another thing to look would be to check if you are creating two much flow files
as this hammers the disks. If you see very high memory usage it could be you
are having to much data in attributes and not in the content of the flow file.
> On 8. Feb 2021, at 07:07, nathan.engl...@bt.com wrote:
>
Hi Asmath,
In terms of performance tuning, I’ve found a lot that needs to be considered.
I’ve done tuning it’s mainly been caused large queues building due to the
read-write queues on the content repo disks being very high. I’ve also had
previous threads on the JOLT default transformation,
Hi,
I am looking for some information on how to improve performance of our
flows. Any suggestions?
1. how to troubleshoot which processor in the nifi is causing an issue?
2. What is the best way to increase the threads or tasks for a particular
processor?
3. How to debug the flow when there is
