Hi,
Why is creating a new thing costing 1.12WU according to bubble activity types“each thing written to or modified in the database” should cost 0.5?
Please see my screenshots.
there is a ticket entrance cost plus the cost of the field update
It costs 0.5 WU to create a thing in the DB.
’Create a thing’ is a Server Action - it costs 0.6 WU for every ‘sever action’ run.
’Create a thing’ also returns that thing to the client - it costs 0.015 WU for every thing returned (plus a bit for the data itself).
So, it does indeed cost (approx) 1.12 WU to create a thing.
3 Likes
Unfortunately, in this Bubble scenario, the costs are extremely high. They really need to update their pricing model—it’s outdated for 2025, and by 2026 these limits and costs will be even more inadequate considering the pace of technological advancements.
@fede.bubble
the starter plan that costs $32/mo gives you 175k WU, the action here in the thread takes ~1 WU. It doesn’t sound high to me but I guess it depends on the type of app and how data intensive it is.
Mind sharing more on why this is the case? Do you mean there are platforms out there with better pricing?
1 Like
@gabriel15 create a new thing is 1.62 WUs, not 1.12…you can use the Data API to reduce that to around 1.25WUs and save roughly 23%
In every test I ever run, even just now, I still get 1.62 WUs on the click of a button to create a single new thing in a custom data type. This has not changed for me in over 2 years. What I do see now though in the logs tab when clicking into the charts to dig deeper is that the Workload by Activity where my breadcrumb is Overall/Workflow/Button is clicked and I see the Create a new thing, when I click into Create a new thing, it just goes to the actual action, so no further breakdown of all 3 major components that make up the 1.62 WUs.
When I go into the LOGs I see the Logs so the Create a new thing action is listed as 0.62WUs and the Button click ‘finished running workflow’ total is 1.62
This has been my finding consistently. If others, @fede.bubble @adamhholmes are experiencing differently, please let me know. I’m a little fuzzy on what the breakdown is.
I do know, or at least my tests show, the same costs for making a change to a thing…however, if the thing is not actually getting changed (ie: all field values are the same as they are or field values are not present in the make changes action) that the cost is only 1.12 WUs, likely because there is not the 0.5 WU cost of Writing to the Database.
@gabriel15 There are also the standalone WU tiers you can add on, so like $20/month for around 200K WUs I think.
From my experience the most cost intensive in terms of WU consumption apps face are fetching of data and creation of data. Depending on the type of data created and when, there are ways to significantly reduce those costs, and depending on type of data and frequency and use case for the data to be fetched, you can significantly reduce those as well. In fact, a paid Plugin I built Data Jedi can help reduce bulk creation and fetch by around 95-99%.
The real magic is the Hybrid Data Structure in which you save API Objects as list field in custom data type (various other ways as well, such as option set attribute or even a file) and the use of JSON for creating objects or modifying client side before saving to database. Lots and lots of great use cases in terms of data and use cases for how that data is to be used. Just takes a bit to wrap the head around how to implement the Hybrid Data Structure properly.
2 Likes
It depends on whether you’re logged in or not.
For a logged in User it costs 1.12 WU to create a thing
For a non-logged in User it costs 1.62 WU to create a thing
The same for ‘Make changes to a thing’
4 Likes
Do you know what’s the extra 0.5 is for if user is not logged in?
@fede.bubble do you know why there is an extra 0.5 WU charge for non-logged in users in create or make changes to data actions? And also, where in pricing guide or manual this is stated? It kind of makes me what to throw up as I do not see what could be the reason for it, other than the potential 72 hour cookies where Bubble will map the non-logged in (who also has to be a non-registered) user to the data they create prior to creating an account within the 72 hours.
If that is the reason for it, is the team working on a putting a simple toggle into the editor so we can declare in settings to ignore bubble built in cookies so we do not need to incur this extra charge for non-logged in users?
Is there really extra compute power required to save changes or create data for a user who is not logged in?
1 Like
Hi, I had already seen your method for reducing the costs of creating and especially searching in Bubble. Unfortunately, I’m not a technically advanced user who can implement and optimize it properly. Bubble should really improve these optimizations natively to reduce search costs.
2 Likes