ayon-frontend icon indicating copy to clipboard operation
ayon-frontend copied to clipboard

Settings: UI very slow, e.g. Maya settings

Open BigRoy opened this issue 1 year ago • 3 comments

The Settings UI for me is very slow and also often doesn't pick up the 'changes' I make until after a few seconds on the right hand side. This is mostly noticable in the Maya settings.

It's very slow in Firefox - and somewhat slow in Chrome.

In firefox toggling a single checkbox freezes the page for about 2-3 seconds. In chrome it's around 0.5-1 seconds.


The lack of "changes" being registered usually happens for me after Saving changes, and then continuing to edit the settings I'm currently in. Like, save changes, edit some more, the new changes are not registered. I need to refresh the page (F5) for them to get registered. However, it could also be that in some cases it's just too slow to follow along maybe? (especially if e.g. in firefox the behavior follows along with over 2 seconds delay each time). I haven't been able to consistently reproduce the failure of it detecting changes. But this screenshot shows the issue:

untracked_change

I toggled a checkbox - but the state change doesn't appear right-hand side, and thus I also cannot save the change.


Server: 1.0.8+202403281707

BigRoy avatar Apr 03 '24 15:04 BigRoy

This is a really... complex issue with no easy solution right now. Maya is just so huge that React can't handle the form size.

Me and @martastain have a couple ideas that might help. But they would be quite hacky unless a proper rewrite is on the cards.

Innders avatar Apr 03 '24 15:04 Innders

We were aware of the fact that by migrating settings to react on the web, we'll speed them up overall massively compared to OpenPype (which definitelly happened), but some of the slowness unfortunately translates to individual items them. We have major quality of life improvements for setting as one of the near future Epics on the roadmap, so hopefully we'll be able speed it up even more.

mkolar avatar Apr 10 '24 07:04 mkolar

#784

Innders avatar Oct 07 '24 09:10 Innders

@BigRoy Is this still an issue?

Innders avatar Oct 27 '25 16:10 Innders

Tested just now in Chrome, seems fine. I recall at the time it was much worse in Firefox, but since I started using it less and less it seems fine for me now. I've also since switched to a much faster machine.

It's somewhere under 0.5s now in Chrome. Not sure what the exact time is.

BigRoy avatar Oct 28 '25 08:10 BigRoy