The trigger to buy more capacity is when you’re reaching your capacity limits. In an ideal world, your app would be 100% optimised and there would be a direct correlation between how fast your app runs for users and capacity. Therefore when users complain it’s too slow you add some more capacity and the problem is resolved.
In reality, the problems most people have with performance are more often than not unrelated to capacity but highlight underlying problems with the way their app is built.
From the graphs that show capacity utilisation you’re using barely any of the capacity you already have. So paying more to increase this even further is just going to burn a hole in your pocket. It would be like expanding your garage to cater for an additional car that you have no plans to purchase.
Performance is a funny thing to solve for a couple of main reasons:
A users device & internet connection can have a huge impact on how well your app performs, which is why it might work awesome for some and be unusable for others. You need to try to test your app under constrained circumstances - i.e. throttled internet connection, old/low spec’d device
Everyone has a different expectation of performance.
A good place to start though is to read this eBook from @petter You can then apply some of those learnings to auditing and refining your own app
Josh @ Support Dept
Helping no-code founders get unstuck fast save hours, & ship faster with an expert on-demand