Datastore Problem (Table or Individual)?

Help and Feedback Scripting Support
#1

So, i’ve been struggling with datastore, the thing is, if i use table to store data using the same key it will make saving a datastore takes longer time, but i can load the datastore faster.

however if i use separate keys i can save the datastore faster, but when i try to load it, it will take long time.

btw, i must load about 100+ data in a game. so what’s the best technique in order to save data fast and load it fast too with a lot amount of data, and the data also need to updates real-time, like everytime the value changes i need to store the data.

(Yep, looks like theres no other way than to use autosave and player leave)

#2

Its always best to store data in tables if you can, as there are data limitations and just easier in general to load everything from one script.

#3

yes, but the problem is if the data is saved too frequently it will delay the other datastores.
and if i use different keys the load time would increase.
you have any ideas in how to fix this?

#4

Try to store all data in one table if possible, and save data when the player leaves and when the game shuts down.

#5

i store the data’s in one table, but the owner wants the data to update everytime she changes it.
and the amount of data is massive theres about 100+ data in the table.

#6

DO NOT save data whenever it updates, thats a horrible idea as it will quickly overload.

#7

what should i do then? should i add an autosave? like every 60 seconds and everytime the player left?

#8

I recommend saving data whenever a player leaves and when the game shuts down. There is also a formula for how often you should save data if you want it to save while they’re playing, i think it was something like 60 + Players * 10.

1 Like