Yes, that was one thing I forgot to include! This state is more or less a constant, so there is no specific window where the CPU usage spikes - it’s constantly ~80% with + 20% -10% spikes.
Hmm, one possibility might be a circular property reference. We try to prevent you from doing that with direct property bindings, but there are still some circumstances where it’s possible. If you’re able to, try isolating it down to a certain view/page configuration/etc and start troubleshooting from there.
This definitely isn’t something we would expect - there’s always going to be some load on the gateway from running the Perspective backend, but it shouldn’t be nearly this heavy.
Good to hear!
Our first priority would probably actually be to try to prevent you from doing such things in the first place - they’re obviously not intentional, just tend to happen over time. If they do happen, then they should (ideally) gracefully fail and give some kind of indication about why to the designer.
Long term, yes, the general Perspective debugging experience is something we’re planning to improve.
