There is no direct conversion from server capacity to workload. Capacity is like a speed limit on the highway, whereas workload is the distance traveled.
On new pricing the capacity charts have been removed, how do I know if I am breaking the speed limit?
Past week we were still on Legacy plans, we sudenly had some big capacity spikes.
When looking at both the WU charts and the capacity charts we were able to identify some problematic elements: search based conditions on components, nested search on RG … and able to fix them or find workaround.
There was also some basic search that were consuming an unusual amount of capacity (still waiting for a reply from bubble support on that end).
However the problematic elements that appear in the capacity charts were not the same that were consuming a large amount of WU most of the time.
I’m now wondering how I should monitor my app performance, and identify the elements that are causing issues without those capacity charts?
All of those things that you learned to optimize your app with capacity is very similar to optimizing your app for WUs. You would still use the charts to see where your app is using the most WUs and focus on changing that to save yourself money. There is no ‘slow down’ anymore since they are not putting any sort of ‘cap’ on your app. So it will run as fast as possible. That’s one positive thing about moving to the new plans. They aren’t forcing a limit on you anymore. Does that make sense? Hope that helps a bit.
Thanks for the reply
Im guessing you moved to the new pricing plans some time ago?
Did you notice some significant improvements to the overall app performance
and robustness migrating to the new pricing plans?
Nope, I finally moved apps over last night before the changeover happened. We have spent a lot of time optimizing over the past months though. Didn’t really play with any of our apps yet to notice any differences so can’t comment on that yet!
I have seen an improvement in speed because it no longer hits capacity. That was a huge help for some of my apps. Especially when I just needed it to run heavy workflows once in a while. Like when a user signed up to the app. Then normally it would just be less heavy workflows. So it handles that a lot better. It allows me to scale easier that way. My users never see my app just crash on them like it used to. So, for me, a big help. I am actually still paying the same amount.
The negative side is that there were some things I would be able to do in the past, as long as it was slow, that I wouldn’t be able to do now because it would be too expensive. Not a big deal, just need to make sure I don’t build those types of apps unless I am ready to pay for it.
