[
https://issues.apache.org/jira/browse/NIFI-14708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004449#comment-18004449
]
Michael W Moser commented on NIFI-14708:
----------------------------------------
The NiFi graph will automatically refresh every 30 seconds in your browser.
So, after you do RunOnce on a processor, the graph can take up to 30 seconds to
show the result. You can manually refresh the NiFi graph by hitting CTRL-R or
right click the canvas and select Refresh. I do this all the time, execute
RunOnce and then hit CTRL-R.
If this doesn't help, then I would look at the environment where you are
running NiFi. Are you running containers? Are you clustering NiFi? Are your
nodes overloading CPU, RAM, disk I/O? Performance tuning NiFi is an art, and
there is no playbook that satisfies all scenarios.
> Run Once Is Very Slow
> ---------------------
>
> Key: NIFI-14708
> URL: https://issues.apache.org/jira/browse/NIFI-14708
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Core UI
> Affects Versions: 2.4.0
> Reporter: Cemre Mengu
> Priority: Minor
> Attachments: Recording 2025-07-03 143959.mp4
>
>
> RunOnce generally on any processor takes about 20 seconds. I have attached a
> video showing me doing it from GenerateFlowFile processor.
> This was not the case for 1.x versions. I am not sure if it is related but
> starting & stopping processors also takes a lot of time now (around 5-6
> seconds).
> Any known issues or workarounds about this? Although I consider it a minor
> issue since it doesn't prevent us from using the system, it is really
> annoying when dealing with a lot of processors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
