Question from a developer:
We have a game where there are over 1,000 levels, and we're saving data on each level as a separate key/value pair. Is this optimized, or are there any negative effects to this?
Question from a developer:
We have a game where there are over 1,000 levels, and we're saving data on each level as a separate key/value pair. Is this optimized, or are there any negative effects to this?
In our current data model, very small key/value pairs aren't efficient. Basically, if it's under 1KB, it's still taking up a 1KB slot - it's very similar to file allocation, basically. We'll be updating later this year with a newer data system that will provide better support for small (sub-1KB) data, but for now I would recommend aggregating information for levels together, to make fewer, larger keys.
we can create all of our levels in json format for sync, can we send and retrieving to json file via playfab , whats your opinion is it work or not ?
Hi Brendan, what's this newer data system you were talking about, is it out yet? Thanks!
Yes, it's the Entity data model - https://api.playfab.com/docs/tutorials#entities. The first tutorial on getting started with Entities shows how to use the Object/File systems we've added.
3 People are following this question.
