BUMP.
I am working on an old app that has average response times above the 30 seconds.
The forms in the app keep calling server functions that return search iterators, then, on the client side, they build the content of repeating panels or other UI components.
The app was created by an ex colleague that didn’t follow the “never return a database row object to the form” rule that I love so much (rule number 2 here). He was happy to see the app working decently in a test environment, but after a few years the app became unusable.
If the app console had shown all the round trips, he would have done some optimization.
Now that I am refurbishing the app, in some cases I move the iterations to the server side, while in same cases I just add a q.fetch_only to ensure I get all the fields I need. I would love to have the round trips printed also now: sometimes the speed doesn’t improve, because I miss one column and the round trips keep happening anyway.
The first thing I did was to switch to accelerated tables. The result was that some functions were faster and some slower.
So far I have pushed the response times down from minutes to fractions of second in all the forms I have touched.
Had this FR been implemented, one of these two points would be true:
- refurbishing the app now would be much easier
- refurbishing the app now would be useless, because I would never be in this place