Bubble Issues: App Continues to "Max Out Capacity" With Almost No One On Site

Bugs
21

Hey @brian,
Could you please update us on your current situation?

The fact that you are paying around $600 and your app can’t handle 15 users at the same time is very alarming to me.
So I would like to know if this is a bug or just the current status of bubble performance.
Thanks

2 Likes
22

Hello @brian

I was thinking upgrade to a paid subscription this week, but this post terrifies me. The worst part is that there are several users complaining about this subject, it’s kind of making me regreat something I haven’t done yet :worried:.

Thank you for sharing this info, it’s very helpful. Wish you luck!

23

Hey all,

We responded to Brian privately today, but the summary is that we’ve been working on infrastructure changes in the background, and the instances that Brian saw his app having capacity maxed out was due to a bug in one of the infrastructure changes. (The spikes we looked into on his app coincided with some events that we knew were going on on the backend, relating to our infrastructure updates.) We had already fixed the underlying issue earlier, soon after the first release of this infra update, but we had to trace down that these capacity spikes were indeed explained by that earlier rollout.

So, in short, we believe this particular bug was fixed. Thanks everybody for their patience as we roll out infrastructure improvements - they’re all groundwork for near-future performance improvements, so hopefully soon folks will think this was all worth it.

(For those who aren’t as familiar with Bubble yet - yes, paying $600 for additional capacity should definitely help you handle 15 users at once, as it’s actually quite a bit of extra capacity. Brian’s stark, odd-sounding case here is what prompted us to dig further and identify the root cause.)

Thanks,
Allen

10 Likes
24

Great news - Thanks @allenyang

25

Thanks @allenyang for clarifying things up

26

Thanks @allenyang. I’m not sure I fully understand what the underlying issues were (I’ll PM you on that one), but I would suggest that the simple solution of having someone look at the back end infrastructure changes as a potential cause here weeks ago might have saved everyone a bunch of time and hassle.

I reported a real issue here - several times - and had to spend weeks getting someone to even have a proper look at this.

Like everyone else, I’m happy there are system improvements on the way soon, but I think there’s definitely room for improvement here on how reports like these are handled - especially when they relate to “known issues”.

2 Likes
27

This topic was automatically closed after 14 days. New replies are no longer allowed.