24
Slow performance on Save/Preview for both apps
complete
J
Joe Hutchins
My app only has ONE page and performance is VERY SLOW whenever i save or preview my page. I came across this post (see below) in the forum in which @Mari from the team discussing performance issues. They said this was caused by large project sites using complex formulas and combinations with the rendering logic of components (visibilities)
Mari also reached out months ago to my first question in the forums (see below).
This was in regards to binding the Visible field for dropdowns to a conditional formula so other components can SHOW/HIDE based on the selected value, rather than using the SHOW/HIDE components from the marketplace. It works perfectly for my case, but now they are saying might be the cause?...
My app is not that complex and I have 5 more sections to add THIS WEEK that have similar formulas applied to each model. I stripped down v4 of my app to only ONE MODEL and still the performance is slow when I save/preview. I’ll send over the two version app ID’s for review.
Client runtime – 3.4.4
v4 (one model) App ID – 339656
v2 (all models) App ID – 318498
Log In
T
Timo Kapanen
complete
T
Timo Kapanen
We have published database upgrade while ago. That is addressing this issue. I am closing this ticket now, please create a new ticket if there are still similar issues.
T
Timo Kapanen
Hi Joe Hutchins, Dominik Greene, sorry for the long delay getting back to this and the inconvenience caused by the slow saving performance. There has been few improvements during the spring time. We also just did a database upgrade which is addressing the saving performance. How is your experience currently? Best Regards, Timo Kapanen
W
William Cromie
brand new app running the tutorial: it's super slow to save. Like, astonishingly slow.
D
Dominik Greene
It does seem to be an issue with conditional renderers (CRs). I have more than one page currently present, but I was experimenting initially with developing a single-page web app where all functions such as the main feed, profile, TOS/other policies, and a few other "pages" would instead be containers with visibility controlled by the CR.
Alas, by the time I hit about six containers in the CR, the app saving and web preview loading process time has tanked to at least a minute, whereas it might be less than seven seconds on our other multi-page (no CRs) web app.
I finally stripped out the main CR and have started migrated each major function to its own page. Performance has increased slightly but I do still have one CR set up as a pop-up type of function in the initial page, so we'll see if that is the problem still once I remove it...
I haven't tried the one-page approach with simple Boolean controls yet set up in a similar manner as CRs, but I'm sure debating it. Will update when I've figured this out.
Kristian Gerkman
in progress
T
Timo Kapanen
under review
T
Timo Kapanen
Hi Joe Hutchins and thanks for your report. I am passing this for our development team to study. Best Regards, Timo Kapanen
J
Joe Hutchins
Timo Kapanen: Thanks! Please keep me updated on the results as the project deadline is quickly approaching, and would like to continue to use AppGyver for the application
J
Joe Hutchins
Timo Kapanen: Just checking in to see if the dev team is still looking in on the performance issues of the apps?
J
Joe Hutchins
Timo Kapanen: Hello? It's been over a week now since I've heard anything.. Also, please note that there will be 10 concept models which will have their own separate page variables bound to each component, toggles etc.
J
Joe Hutchins
Timo Kapanen: 3 weeks and no response?? This does not bode well for the AppGyver team 😒
Kristian Gerkman
Joe Hutchins: Hey, sorry for the delayed answer!
There is a potential fix for this in the release pipeline now, and will be released later this week or early next week.
Also we've prioritized Composer performance higher, so there will be incremental performance improvements coming in the upcoming updates.
Thanks,
Kristian
T
Timo Kapanen
Joe Hutchins: like Kristian indicated, we have published an improvement on last Friday. Could you check if it helps the performance with your app. Sorry for the inconvenience this has caused to you. Best Regards, Timo Kapanen
J
Joe Hutchins
Timo Kapanen: Thanks for your reply. There's a 'slight' performance boost when I preview the app, but saving in Composer itself is still slow. Sometimes im waiting 10+ seconds for the apps to save. I'm just worried that if I keep adding more page variables/components that it would cause Composer to crash, don't want that! I'm also on WiFi connection when I work, so I'm not too sure if that could also be the case?