Basic Performance Issue: Professional Plan(s), Reserved Capacity, and Time-to-First-Anything-Throttling

Hi @neerja,

I could certainly provide a copy of my app as it exists today, I suppose. But note that of course the behavior I’m describing really only happens with apps that are in production/in use and are consuming Bubble resources.

As far as what happens with my particular app (this is the GRUPZ app that I’ve shared with you terrific support folks in the past when I’ve had bug reports), the Logs tab from today is a pretty good illustration:

What we’re looking at here is the past 24 hours on a Professional app with default 2 units of capacity. While there are no periods where the app seems to have reached max capacity, there is of course the “your app could have been x minutes faster” note.

And in my specific case, it’s suggesting that it could have been a total of 70+ minutes faster over that period with more capacity. (How much more capacity I’d need to add remains a bit of a mystery.)

Looking at the server capacity usage chart for the period from early this morning to about now, we see Web Requests represent the bulk of used capacity (the green segment is Scheduled Workflows at 10.1% of used capacity):

Drilling into web requests we see Page Load at 5.1%:

Fetching data at 21%:

The pink segment is “Other” at 65%.

Looking at Page load metrics (last 60 minutes as that chart shows) we see:

I’m not really sure what to make of all this, but in short, my app goes through short (and unpredictable) periods where web server response is slow. (The most noticeable feature of this being that one can observe an obvious delay where the browser is waiting for the response from Bubble to fetch Bubble’s initial page load scripts and stuff.)

And, as you can sort of see from the shots above, the number of pageviews in the past 24 hours isn’t enormous. Looking at Google Analytics data for Nov 18 - 19 just now, I see:

Of course, pageviews aren’t the only HTTP activity going on (we’re consuming data from external API’s and such).

This morning as I’ve been working with this app, page loads / page navigation has mostly been quick, with occasional times when I see “waiting for dhtiece9044…”.

Basically, the web server response is “lumpy” :slight_smile: