I’m implementing Playfab for my game, and I’ve been studying documentation these ast few days and this question isn’t clear at all from all I’ve read.
In your Consumption Best Practices pages it is implied that sending a lot of data writes with less than 1KB is not good, as each write has a minimum 1KB and this results in doing more writes than necessary. Thefeore, do fewer bug bigger key-value pairs. Which was enforced by several answear posts by your staff.
Ok. That’s how it was with PlayerData, the old system. But then there are posts talking about the new Entity Objects and how they, among other virtues, boast being good for small entries. Therefore, we can do small key-value pairs.
And I wanted a definitive answear about the best practice using Entity Objects: do I make my system send few big key-values or can I make small key-values?
The way my game is being done, I can do either. I can do a big key-value pair and send it all in one go, including within data that wasn’t updated. Example: making a big key-value pair containing all bools used in my save system. Game reads/write with low frequence, but when it does, it sends all booleans, regardless if they changed since last update or not.
OR I can do a small key-value pair for each variable. In the same example, with the same read/write frequence, I’ll send all booleans that were updated. There will be more calls (various small keys), but the overall data will be smaller this way. Using entity, which way is the correct?
