Ahhhhh… the ole’ confusing Bubble Capacity issue. Ugh.
Here is what I know:
Every app is different. One may use X capacity to support x users and another may use ten times the capacity to support the same number of users.
Do the temp capacity boost and apply a load. Review your charts and you may be able to come up with an estimate. But that’s all it really is - an estimate. This is a sore spot with me - Bubble does not make clear what a CU really is.
For what it’s worth - we find from only estimation (because the app is not live yet) that 1 Bubble CU would support apx. 70-110 users. So much is at play here - including the target geographic location on users which alters peak times. Are all the users in 24 time zones or 4? etc.
Reduce searches where ever possible. When multiple searches are needed put the elements in a group and apply the search data to the group and refer to parent.
Just my two cents. I may think of something else and come back to edit.
**EDIT two minutes later:
Another thing is this. A simple page load in Bubble seems to consume a lot of capacity. So when you think of marketing and conversion rates this becomes an issue. If you have a 5% conversion rate you would need at least 100 index page loads to achieve this. We found that presenting a landing page using Bubble index page is terribly inefficient. Instead, now the public facing site including all landing pages, FAQ, about, contact, etc. are on the main domain with html5. The pages load blazingly fast (compared to Bubble) and do not use Bubble capacity. We moved the Bubble app to a subdomain. Now, any Bubble resources that are used will be used only by customers who have already converted and not the 95% of those just looking.