Hi! I found out that Firefox is much performative for the NiFi UI than Google Chrome.
Best Regards, > On 7 Sep 2021, at 09:59, Matt Gilman <[email protected]> wrote: > > Josef, > > There was a regression in Chrome 92.x that affects SVG heavy web applications > like NiFi. Here is the Chrome issues tracking this [1]. And here is a Chrome > Help thread discussing the matter [2]. > > [1] https://bugs.chromium.org/p/chromium/issues/detail?id=1235045 > <https://bugs.chromium.org/p/chromium/issues/detail?id=1235045> > [2] > https://support.google.com/chrome/thread/118284571/any-one-suffers-from-the-newest-ver-92-rendering-some-heavy-svg-jobs?hl=en > > <https://support.google.com/chrome/thread/118284571/any-one-suffers-from-the-newest-ver-92-rendering-some-heavy-svg-jobs?hl=en> > On Mon, Sep 6, 2021 at 10:12 AM <[email protected] > <mailto:[email protected]>> wrote: > Hi guys > > > > We can confirm the slow browser behavior as well and it’s very annoying. We > have single node NiFis as well multiple NiFi clusters with different sizes. > It happens everywhere and is definitely browser specific. We’ve also tried to > restart NiFi, but no change at all. It so slow that in 2-Node cluster and a > PG with 300 processors it sometimes takes longer than the browser timeout to > just ENTER the PG. > > > > It happens with Chrome 92.x and as well with Edge 93.x (both based on > Chromium?). Firefox is way faster -> we switched over to Firefox. We don’t > exactly know when the issue started, but we have definitely just slightly > modified our workflows in the last 2-3 months and we were using NiFi 1.13.2 > and the same Java Version since multiple months. We are working with NiFi > since 1.4.x, so we are not new into NiFi. > > > > We see that memory goes up fast when we try to open a PG with Chrome, but we > don’t know what’s normal. > > > > To answer Marks questions: > > It’s faster when we zoom in/out in a way that NiFi stops rendering the stats > GUI refresh for a single NiFi PG with 30 processors takes 2-3s while the logs > shows at max 40-50milis for the GET. > Network is fast as hell, no change there. As Firefox is way faster than > Chrome/Edge I don’t think it’s a connectivity issue. > - NiFi 1.13.2 > - Java 1.8.0_282 > - In “bigger” PGs with 300 processors it takes more than 10s to open the > flow. Most of the time the browser windows crashes due to long timeout. > > > Hope this helps. > > > > Could it be that Pierre referred to this issue/improvement for NiFi 1.15.0? > > https://issues.apache.org/jira/browse/NIFI-9061 > <https://issues.apache.org/jira/browse/NIFI-9061> > > > For us this is a major issue, but as we have a working alternative (Firefox) > we didn’t raised a jira ticket yet. > > > > Cheers Josef > > > > > > From: Mark Payne <[email protected] <mailto:[email protected]>> > Reply to: "[email protected] <mailto:[email protected]>" > <[email protected] <mailto:[email protected]>> > Date: Saturday, 4 September 2021 at 15:55 > To: "[email protected] <mailto:[email protected]>" > <[email protected] <mailto:[email protected]>> > Subject: Re: UI is not as responsive... > > > > OK so there are really 3 parts to consider here in order to understand what > is making things sluggish: > > > > - Front-end rendering > > - Backend processing > > - Network between your browser and the back end > > > > So a few things to consider here: > > > > - If you’re seeing the sluggishness in a Process Group with only a few > elements, that leads me to believe it’s probably NOT the browser rendering > that’s an issue. But another thing to check, to help verify: zoom out using > your mouse wheel to the point where NiFi no longer renders the stats on the > processors. Once you reach this level of zoom, the rendering is much cheaper. > Do you still the same lag, or is the lag less at this point? > > > > - To understand how long the backend is taking to process the request, you > can add the following to your conf/logback.xml file: > > > > <logger name=“org.apache.nifi.web.filter.TimerFilter” level=“DEBUG” /> > > This will cause nifi to log in the nifi-app.log file something like: > > GET /flow/1234 from localhost duration for Request ID 4567: 102 millis > > > > So watch the logs here. Are you seeing the request times in the logs are > constantly very short while the UI takes a long time to render the request? > > > > - Do you have any idea what kind of latency and throughput you expect between > the machine running the browser and the machine running nifi? > > > > Also, a few other things to understand: > > - What version of NiFi are you running? > > - What version of Java? > > - When you say the UI is not as responsive, what kind of delay are you > seeing? 1 second to refresh the UI? 10 seconds? > > > > Thanks > > -Mark > > > > > > > > > On Sep 3, 2021, at 1:42 PM, Jean-Sebastien Vachon <[email protected] > <mailto:[email protected]>> wrote: > > > > Hi Mark, > > > > thanks for the quick response. I am running a single stand-alone Nifi > instance (1.13.2) > > I tried with a smaller group (1 input port and 8 processors), and I still > experience slow downs. > > > > I've looked at the timing of the backend calls and everything seems in order. > > > > I am using Edge but some of my colleagues are using Firefox/Chrome and > experienced the same. > > > > One of the flows we are dealing with is relatively complex and involves about > 50 processors. > > I will try to split it into smaller groups and see how it goes. > > > > Thanks > > > > Jean-Sébastien Vachon > > Co-Founder & Architect > Brizo Data, Inc. > www.brizodata.com > <https://outlook.office365.com/mail/options/mail/messageContent/www.brizodata.com> > From: Mark Payne <[email protected] <mailto:[email protected]>> > Sent: Friday, September 3, 2021 1:19 PM > To: [email protected] <mailto:[email protected]> > <[email protected] <mailto:[email protected]>> > Subject: Re: UI is not as responsive... > > > > Jean-Sebastien, > > > > Are you running a cluster or a single, stand-alone nifi instance? The > slowness could be either on the backend (performing the action and > formulating the response to the UI) or on the UI end, where it has to render > everything. > > > > One thing you can do to help understand which is causing the slowness is to > create a new, empty process group and then step into it. Is the UI still > sluggish when you’re in that process group, or is the UI faster there? Also, > which browser are you using? > > > > Thanks > > -Mark > > Sent from my iPhone > > > > > On Sep 3, 2021, at 1:03 PM, Jean-Sebastien Vachon <[email protected] > <mailto:[email protected]>> wrote: > > Hi all, > > > > The UI has been slowing down considerably over the last few days/weeks. I > tried restarting Nifi but it does not really make any difference. > > I tuned the JVM and there is no sign of heavy GC going on. > > > > What other things should I investigate? There is currently around 4.2 MB of > data in all my flows... so not much going on and it is still slow. > > > > My server as 128 CPUs and 512GB of Ram of which 15 are allocated to Nifi. > > I do have other processes running but nothing to cause any slowdown. > > The load on the server is around 25 and is 98.5% idle. There is nothing going > on regarding storage as well. > > > > Thanks > > > > Jean-Sébastien Vachon > > Co-Founder & Architect > Brizo Data, Inc. > www.brizodata.com > <https://outlook.office365.com/mail/options/mail/messageContent/www.brizodata.com> > >
