The issue is not related with queries and Collections. It's the internal gateway between PowerApps and Azure SQL that slow things down. I only use Collections and my queries used to load them are optimized.
Anyway... I hadn't any report from users on my side about slowness. I think the PowerApps/Azure teams figured it out.
What do you mean by your queries are optimized and you only use collections?
Do you mean onstart -> load all necessary data to collections?
I mean I apply filters on columns with proper indexing and never load a lot of rows. On average my queries returns no more than 50 rows.
To load everything onstart causes the app to spend a long time starting. A best practice is to load ondemand according to screen usage or using the timer component.
Most of my loading time is spent on onvisible events and besides that I try not to load a Collection twice unless necessary.
Same problems here. It´s also a frustrating experience to patch a row to the Azure database. Sometimes it needs only 0.2 seconds and then it needs 28 seconds to write a simple row to the Azure database.
Check out these cool Power Apps & vote on your favorite!
Let's talk about the solution provided by Microsoft for Robotic Process Automation (RPA)
Check out whats happening in Power Apps
FIll out a quick form to claim your community user group member badge today!