Is 6 seconds between write requests a server or experience limit?

when we look here Data Stores
we see that it says there is a limit of 6 seconds between write requests when using the same key
and to me it looks like its a limit per server


but when we look at the new beta documentation here Data Stores | Roblox Creator Documentation
now it looks like its a experience wide limitation
image


so what documentation has the correct information?

If the new documentation is correct then that means the code below would hit the limits once there where more then 1 server

local dataStoreService = game:GetService("DataStoreService")
local dataStore = dataStoreService:GetDataStore("Store")
 
while true do
	dataStore:SetAsync("Key", true)
	task.wait(6)
end
2 Likes

In this case, I believe it would be the server. If you try to call any function of a datastore too much in a server, it could overload it and cause an error. There is no experience-wide limitation besides how much you can store.

I would say maybe the new documentation made a mistake but they have a full paragraph saying

The following functions have experience-wide limits that apply regardless of which server calls them.

So now I’m confused because I also always assumed it was a server limit but now the new documentation has me questioning myself

From my experience, it doesn’t matter how much another server calls the datastore, it won’t affect the other server. There may be something, but I believe that it will only error on the server/have an effect on the server that had called it too many times. Now, if there was an experience-wide limitation, it would probably be SetAsync, RemoveAsync, or UpdateAsync. If you call these too much, chances are that the queue would get too long and it would error. Now as for the limitation I was talking about, it would most likely be on specific keys of the datastore. Trying to save/update the key too much will cause errors and also cause dataloss.

Sorry I should of explained it better the 6 second limit is only when you use the same key

So I’m aware that if you try to write to the same key within 6 seconds it will be added to a queue and if the queue fills then the request will fail

But my question is. Is this a server limit or experience limit because according to the old documentation it looks like a server limit but according to the new documentation it’s a experience wide limit

It’s an experience limit, it was recently changed on the new documentation to avoid confusion but not changed on the old documentation as that is not being updated.

1 Like

This changes everything i guess I’ll need to save the data into a new key every time and keep track of the key using a ListDataStore the same way datastore2 does

1 Like