SetAsync() and IncrementAsync() are also inherited from GlobalDataStore but they seem to have a separate SetIncrementOrderedAsync budget when working with an OrderedDataStore.
Is that just inconsistent or is something else going on?
IncrementAsync is a “get then set” though it is not documented on the api if this is an atomic action.
So the operation cost is greater than SetAsync which inserts or replaces which can often be done in one database action e.g. for mysql INSERT … ON DUPLICATE KEY UPDATE.