(I am using the open source ProfileService for my data saving as provided by Loleris)
I’m a little bit confused on datastore limits, I’ve sometimes had the warning where the request queues were stacking but ultimately no saving issues. However I am little concerned on how I’m approaching this:
I’ve got a placement system for furniture for a project, where it saves a serialized CFrame & Color3, object ID and a rotation number. See below as to how it’s represented:
“10” is the placement Key and everything else is presented in a dictionary format.
This is just for 1 piece of furniture. This is the most efficient I can possibly think of to save the furniture. I am going to limit a players placement amount to 50 or 70 (ideally I want to increase this cap), but I found that Adopt Me can spawn an unlimited number of furniture when I tested it.
When saving data, is the size of the player data considered when requesting to save? Right now, when I use:
HttpService:JSONEncode
The returning number on the current data says 8000+, this is with 20 pieces of furniture plus other pieces of data such as cash, clothing data, outfit data, item inventory. Below is the limits presented in the developer hub:
Would the datastore fail to save such large data? Or does this not matter, and it’s the volume of requests that really matter. Note that I am using ProfileService for this, but a general guidance on this would be appreciated! Thanks!


