@zito@lizlynch Is it normal that on a browser (Have not tried on Mobile) that if I multiselect about 50 rows and click a simple action like adding the Text “Go” to a specific column for all 50, the browser lags and only after about a minute and a few times clicking browser to “Wait” then I only see the 50 Syncs appear…
Our users cannot understand it is busy and are tempted to feel the Tab is not responding…
Can this please be addressed and also if anyone else is facing Browser lagging on multiselect actions please do chip in here.
I tried running a “set column value” action that sets a column value to “Go” on 50 rows in a simple app in desktop Chrome, it took about 10 seconds. This is probably close to the lower bound. There are probably things that could be optimized in there, but if you’re seeing it take over a minute then I suspect the difference is related to the number of computed columns in the row and/or having a few particularly expensive AppFormulas. Whenever a row is updated it triggers a recompute of all AppFormulas in the row (as well as things like change-triggered columns or reset conditions).
For those of you seeing such long delays, can you try comparing the time it takes to run it on 50 rows vs the time it takes to run it on 10 rows, and see if the difference is approximately 5x? If it’s just a matter of computing a single row being a bit slow due to AppFormulas and then scaling that by 50x, there may not be much we can do to alleviate that other than maybe show a loading spinner. But if the time to update 50 rows is significantly slower than 5 x (time to compute 10 rows), it would suggest that there’s something inefficient about the way the bulk action is being applied.
When I try this in my simple app I get 2.3s to run 10 rows, which would imply 11.6s to run 50. So the scaling looks roughly linear when AppFormulas aren’t involved.
I do find a nonlinear scaling when certain AppFormulas are involved (such as Select over the same table being modified). Also some other inefficiencies. Let me see what we can do for this.
Just circling back to this, we did roll out some optimizations over the last few months that should have significantly improved the performance scaling with multi-row actions. Hopefully those of you affected have seen some noticeable improvement since the original post.
Thank you and team, I have seen an improvement yes.
I selected 184 Rows and clicked an action to increment my update column [Update] +1
It took about 14 seconds to respond and show 184 syncs, the browser did say my tab is not responding after about 10 seconds however as mentioned after 14 seconds it kicked in, each sync item takes about 1 second to show it decreasing, so it took about 184 seconds to finish the 184 syncs.
This may not be the best way of testing it, but it’s a real life scenario I could try it on.
Whether this is optimal I cannot say, but it definitly improved in terms of the page not responding for long periods of time..