I really need help understanding and optimizing my app’s Workload Units (WU) consumption.
I just launched my app publicly yesterday, and within 2.5 hours it reached 100% of the 175,000 WU monthly limit, which caused Bubble to automatically take it offline.
According to the logs, a single page load consumes around 8,400 WU (5,000+ runs) — which seems insanely high for what should be a normal page load with some repeating groups and workflows. The app (Fanatsy sports game) is working perfectly in terms of functionality, but the workload usage is completely unsustainable.
I’ve already checked for obvious infinite loops, recurring workflows, or list operations, but I can’t find the root cause.
I’d really appreciate any guidance or support from developers experienced with WU optimization — either advice on what to check, or if someone offers professional help to audit and optimize the app.
I’m currently on the paid plan (175k WU/month), but at this rate I’d need tens of millions of WUs, which clearly means something’s wrong.
There are a few posts in the Forum regarding optimizing your Bubble app to consume fewer WUs. At Zeroic, we do app audits as well, especially to support the community. Happy to take a look and see what could be done in your app. Feel free to DM
It sounds like you’re spending a lot of WU on the page load process itself, which is usually related to either 1) loading a lot of database data (complex and possibly numerous database searches), or 2) running a lot of page load workflows.
I’d start there and use the metrics to see if any processes specifically consume a high amount of WU. It’s true that infinite loops etc are a common cause of WU spikes, but keep in mind that frequent page loads are a kind of loop too: you’re repeating queries and workflows a lot if you get a lot of traffic.
In short, don’t fall into the trap of “blaming” workload (not that you are), but just focus on the idea that something is gobbling it up, and in my experience it’s usually a few processes that are to blame for that.
Thanks for your reply on my post about Workload Units. My app suddenly hit 175k WUs in just 2.5 hours after launch, and I’d really appreciate your help checking what might be causing such extreme usage.
If you’re available to do a quick audit or point me in the right direction, I’d be very interested.
Let me know how we could proceed or if you need temporary access to the editor.
Exactly @petter, those two points you mentioned make total sense, and I think what makes the most sense here are page loads that have several heavy database searches.
@23acher, couldn’t you check on the logs page which workflows are consuming the most? Or does it only show “page is load”?
With that in mind, is your app a SPA? Or does it have multiple pages?
Try going to the places where you know you have “page is load” events and check if there’s any kind of complex or heavy search there or something that might be running in a loop.
We should always try to save on “page is load” events, since they literally trigger every time the page loads. In many cases, a “Do when” condition can be more appropriate, but we should use it sparingly too.
The most important thing is to think carefully about how you structure your workflows and triggers, as well as the database design of your app, which directly impacts these actions and their potential WU consumption.
I just wanted to take a moment to thank @Zeroic (Prashant) for his incredible help.
He took the time to meet with me, analyze my app in detail, and quickly identified where the real issue was — which turned out to be something completely different from what I initially thought.
I’m truly grateful for his professionalism, deep technical knowledge, adaptability, and overall kindness throughout the process.
I can’t recommend his services enough — he’s been outstanding to work with.
