Hi guys I am trying to evaluate my scripts to ensure they are expandable and I noticed that SetAsync is limited to 60 + (numPlayers × 10).
I have the below querys i would like to figure out:
Is the limitation based off a single server or all servers in an experience
Taking into account this limitation should save loops be greater or equal to 1 minute to ensure caps are not met
If I were to save every couple of seconds, if I were to reach the cap what symptoms would occur in terms of the data saved
Is the best way to ensure Dev Product and Gamepass Purchase is to have a removing and serverclose event to ensure it saves
If a loop is calling a savedata function and the server closed and runs the same savedata function do they run separately or does the new called function override the last one
Looks like that limit is for each server, not all servers combined.
I personally do 60 - 90 seconds.
I heard it might get corrupted. But i think it’s just that it won’t save until the other requests are fulfilled.
You can do that or just make a request with a delay so it can save without waiting for the player to leave or the server to shutdown but this may be a little risky imo.
In one of my games, they reach the cap (somehow) and it seems only one of them saves while the other is cancelled because the player isn’t in the game to have the data saved so it still saves but one of them gets cancelled.
In your opinion why would you recommend UpdateAsync i have read into it and it seems to be safer only when more than a single server is writing data to a specific key which in my situation it doesn’t apply, would you recommend a mix of UpdateAsync and SetAsync when needed to ensure the server is efficient as UpdateAsync is slower then SetAsync.
