@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.