Understanding Bubble Workload Unit

[val2]

Can someone please help me get a better understanding of Bubble pricing/workload and real-world usage?

Holy Cow, I just got a notification that my app “has hit its maximum capacity usage for 36 minutes over the last 24 hours”. This is astonishing because I am still under development. NOT LAUNCHED. NO USER. Just me building.

I am on already on the Starter plan. Paying! I page view. I am just adding Database triggers and API to support my app use cases?

I am just wondering if anyone can give me a real-world mapping of the Bubble Workload limit, pricing, and app usage/number of users.

For example, can I support 10 users with the Starter price? Can I support 50 users with the Growth Plan? I am building an Invoice app where users enter some information, and that data is passed to an API that generates a PDF and returns the URL.

This is alarming to hit the threshold with less than 10 database items, practical zero page view and a few API calls.

[georgecollier]

The answer is… nobody knows. You have to try and find out. Blame Bubble

[ihsanzainal84]

Read the manual, specifically about Workflow usage, here. It explains what activities contribute to WU.

There’s no exact WU cost for an action as it all depends on how much processing Bubble does to execute that action. There are some consistent averages for certain actions but you’ll have to search around the forums.

From there the best way to go about it is to drill down your logs and find out why those workflows are consuming so much WU and figure out how you can optimize to reduce WU.