Server API limitations
We planned to create game with asynchronous multiplayer support and using playfab for player specific data and external server for computing battles and other specific tasks.
In our case we need to update a batch of users after battle calculated, possibly thousands.
Question: is there any limitations to server call api? What will be if we will try to update 1000 or more players UserData in one second?
Best Answer
Hello,
There is a general rule of no more than 3 PlayFab API calls per second, this is for all API calls. For updating UserData there is a specific limit of 10 UserData updates per 10 seconds. it is required that this data be stored in the Player's UserData instantly or can this data be store over a longer span of time?
Are you telling about limitations for *one* player? Do you want say that I can't update 100 different players statistics or their internal data in one second in playfab?
To clarify, the limits that have been specified are on a per-player basis, and averaged over the life of the session, a few calls a minute should be your target.
Additionally, no title should be making calls per player at this high of a rate, apart from short bursts. Making calls multiple times per second over a prolonged period will result in your title being throttled.
I didn't understand.
Will be 1000 or more calls per second throttled where each call is for unique player.
To clarify:
1 call per player for thousand players.
@Brendan Has the 1000calls/10s server API rate-limit removed along with the new consumption-based pricing? I just do some test, and seems like I could login/register over 5k users within 10 seconds using "PlayFabServerAPI.LoginWithServerCustomIdAsync".
It would be great if we could get a confirmation, as our game will be using an external server to sign in all users, and we don't want it to be throttled during production.
No, the rate limits on the Client and Server API calls has not changed. However, the rate limits are currently enforced on a per-server basis. And since the service runs a great many servers for load balancing, it is possible to exceed those limits from time to time.
