Solutions for app optimization?

Hello, our app is becoming slow for our users. I am thinking it is because we have a lot of database queries that are all running at once. We have upgraded our capacity before but I’m not sure if that will help more than reducing query load.

each of these capsules have 3 separate queries with some of them having logic with them.

Is a query summing up some of our metrics faster than bubble summing them up?

Or if you have any thoughts about speeding up apps in general I’d love to hear your thoughts!

Hello @jordan8

Performance is one of the tricky subjects and a good start is to qualify WHERE specifically it is slow?

Is it the page load – may be too many elements, images.
Is it the search – database issues then (which I think what you are suggesting ?)
Is it navigation – Workflow logic may be.
At Specific times – Check the CPU Graph in your account settings and see what is causing the spike. Unless its always spiking don’t upgrade yet. Other may disagree but I would try to optimise on a standard plan rule out all logic issues before buying additional CPU.

Once you know WHERE it is slow then look at WHAT is causing that. For example if it is data retrieval, running a test by using an external database through an API might rule DB searches as the reason(from my experience bubble is great at building good apps fast but not for complex database operations). External DB can be indexed and bubble database can’t be.,

Further idea on slower bubble queries is to somehow spread the queries out and organise data better. Bubble is no code platform but is still programming and a good dev can split the data and query logic for optimal search.

All the best.


You could do following to increase performance:

  • query database in fixed intervals, like 30min.
  • save the results
  • display the results

This will prevent a query everytime someone wants to see the graphs.

1 Like

Okay I’ll try to dig into what is slowing down my application a bit more. The graphs aren’t spiking too much and look into our logic a bit more. Thanks for your help!

We only need to query once the user loads the page the first time. We have thought about saving the results elsewhere so we only have to query once rather than every time a user switches a field or loads the page.