It is very responsive at the moment in the Midwest US. - Thanks
Are there any more does and donâts regarding performance?
What Iâve done so far:
-
Reduced workflows in my header (reusable element). It was just 2 simple conditional Events but made a huge impact on initial loading time. However, it also reduced the UX a bit.
-
Setting up Element States with Thing data, and then changing the states when the user interacts with the page. This made the click response immediate. I also update the Thing since I need that data on other pages. This is done in the background and the user isnât affected. I learned to restrict the use of things and instead use states when make a real time game in Bubble (soon to be released).
-
Iâm still struggling with repeating groups lagging when loading 2 simple rows of text from a database with 2 objects. I have a popup with a repeating group that show a list based on the selection on the page. When the popup is shown it first shows content from the last time it was popped up, and it takes several seconds for it to update with the new. This, even though I tried to preload the repeating group content.
-
I have a menu icon in the header (reusable elements. It shouldnât be visible when the user isnât logged in or when the user havenât selected object to work on. (Before I handled this through a conditional âPage is loadedâ-event making a page redirect, see above). I put made the icon not on page load and put a condition on it to show it when appropriate. This made the icon appear long after the rest of the page (even the repeating group with the images). So now I always show it on page load and have a conditional âPage is loadedâ-event i the header hiding it when it shoud be. That may take a while but thats the more seldom used use case so itâs ok. So now the user in the common use case gets the menu fast.
-
To sum it up so far; make sure UI components are shown first, make UI components respond without database-access if possible, and make database updates secondary since they will be carried out in the background.
Will keep workingâŚ
Hey, I am getting saving problems in bubble again. Anyone else experiencing issues? Anything important to be aware of?
Sorry for the issues todayâweâve been steadily working on isolating apps on the shared cluster from impacting each otherâs performance, but a corner-case came up today where certain types of heavy activity can degrade overal system performance. Weâve released some fixes to minimize the effect, and we should be able to eliminate it altogether something in the next few hours. You can see the issues reflected here: status.bubble.is
no worries. Wasnât sure if this was something that was known/common. wanted to bring it up just in case. Thank you for the quick reply!
yep, fair enough. anyway I think we are good now â stats are back to normal, and it looks like the new containment measure works properly.
EDIT: well, I might have spoke too soon â still seeing some latency spikes⌠tracking them down though.