Datastores: Unclear that "UpdateAsync" budget is actually minimum of set/get budget

[buildthomas]

As described here: (linked by section)

Details on DataStoreService for Advanced Developers

Table of Contents Introduction Request Flow Overview of Limits & Budgeting Budget Consumption Budget Limits through Command Bar / Plugins Notes on Caching Notes on UpdateAsync Notes on OnUpdate Conclusion 1. Introduction This is a complete, comprehensive overview of all sorts of implementation details and gotchas regarding Roblox’s datastores from the perspective of the DataStoreService API that are not properly described on the Developer Hub at time of writing. The reason for writing is tha…

---

It should be documented on the wiki that:

local DS = game:GetService("DataStoreService")
DS:GetRequestBudgetForRequestType(Enum.DataStoreRequestType.UpdateAsync)

Actually just returns the result of this statement under the hood:

local DS = game:GetService("DataStoreService")
return math.min(
   DS:GetRequestBudgetForRequestType(Enum.DataStoreRequestType.GetAsync),
   DS:GetRequestBudgetForRequestType(Enum.DataStoreRequestType.SetIncrementAsync)
)

Otherwise, suppose that the set budget is 500 and the get budget is 100, people might get confused that they don’t see the UpdateAsync budget go down whenever they perform an UpdateAsync call repetitively on the same key (because it would reduce only the 500, so UpdateAsync budget would still be 100 afterwards).

See linked post above for reasoning on why this is implemented this way. Simple tests with consecutive datastore calls can be constructed to show that this is indeed the case, or ask an engineer to verify the implementation.