desktop studio performance

[Anonymous]

I have an app that connects to a list that has about 30 columns.  I'm rendering an edit form that displays about 25 fields, with the other five being shown only based on certain conditions.

In the desktop studio, it is almost impossible to work on this screen - clicking on anything takes 5-10 seconds to alter focus, writing formulae is basically typing for 5 seconds, waiting for 20 seconds.

I've disabled auto-save and started saving locally just to try and make it usable.

I have windows 10 on an i5 laptop with 16GB of RAM.

The web studio at this point is much faster than the desktop studio, so I'm now editing there instead!

It sometimes feels like studio is running about a million processes every time I do something - whether it's the intellisense or it's checking back with the cloud I have no clue, but it is honestly impossible to work (and demonstrate) to users using desktop studio.

I'm going to start moving my gallery data sets into collections to check on performance improvements there, but unless it's just the scale of the web studio backend that makes it faster, I suspect something within studio....

Any comments, suggestions or ideas welcome!

Kind regards,

R

[mx]

I'm having the exact problem ... and it's totally maddening, and basically unusable ! I have a SuperFAST Dell Precision M4700 with one of the fastest Intel i7 processors on the planet, 32GB ram and 1TB Samsung Pro SSD. This issue seems to have to have gotten worse with the latest release of PA Desktop Studio (v 2.0.704 - with the new Rules enhancement. I just noticed I have AutoSave on as well ... turning it off to see if that helps ... will report back. I'm also noticing that PowerApps is taking up a GIG of memory !

[Anonymous]

I'd be happy for it to take up 10GB as long as it was fast 🙂

[mx]

For sure .... This MUST be a known issue.

[Venxir]

I'm experiencing this problem too. The studio becomes completly sluggish when you're building something a bit more fancy than the average form input. Memory goes up to several Gigabytes and my Kaby Lake i7 goes to 60% cpu just to switch the properties of a control.. 

I wish you could disable that hybrid runtime in design time, i'll see the results when i preview the app.

[mx]

Yes an option to turn OFF the Runtime in design would be good.

[JRaasumaa]

I'm in the same boat as all of you but nothing has been mentioned by Microsoft or the PowerApps staff to acknowledge the poor performance. I think a lot of the slowness is similar to how Access or Excel try to autocalculate every single button press.

https://powerusers.microsoft.com/t5/PowerApps-Forum/Powerapps-is-too-slow-to-actually-use-day-to-day...

It's incredibly frustrating knowing that the app that is supposed to replace all these other technologies can't even keep up with a moderately complex app without slowing to a halt while editing, it's so bad that at times my typing shows up 1 character every second or so...

To vote on turning off the real time code execution check out:

https://powerusers.microsoft.com/t5/PowerApps-Ideas/TOGGLE-Real-Time-Code-Execution-in-Development-S...

[bishoy]

same here

[mx]

Update:
In the Web 'studio', this performance does not seem to exist at all. No issues per se.

EXCEPT the uber annoying 'Your Session has timed out issue' ... when you are ACTIVELY working in the UI.
Supposedly this was fixed (?), but apparently not.

Note that my Web version is 2.0.702 ... and the Desktop Studio version is 2.0.704

[Anonymous]

I'm editing exclusively in the web studio now - besides much better performance, it also saves camera images as data:image/jpeg;base64 as opposed to completely useless blob:xxxx, which desktop saves them as -  only relevant for my current app, but annoying enough to vent here . No clue why web and desktop are different in this respect, but they most certainly are.

The autosave feature is fast online, so this helps to alleviate the session timeout irritation - had to rely on it three times today already and was pleasantly surprised.