Experience Key Value Pair. Data Quoter and Call Throttle values

[Gunwald Constantine]

Does anyone know where I can get data on these? Data Quoter and Call Throttle values?

I already have script using dynamodb with a server, but i am working on something that just needs to store user data over processing it all.

But without knowing values for experience key usage, I am unable to know if it will be limiting or not and i should just stick to own solution.

Edited August 26 by Gunwald Constantine

[Lucia Nightfire]

Without mentioning specific rate values, Experience KVP r/w is far more generous than HTTP in/out as far as throttling is concerned.

You might need to be more specific where you concerns lie.

[Gunwald Constantine]

Thank you for reply.

Well, trying to decide how i structure it. But decided keystore is to limiting for what need.

I also thought could do wildcard search to find keys, and values but realized that is linksetdata so will be to hard to organize, which would be one request. but without that would be possible 100-500. which would be way to many. As well with key size + script memory limits would mean even more requests. 

So decided not suitable whatever the top limit is, will just be to much data/requests.

Also no way I can paginate any key value requests.

 

One i did find, for anyone reading later,  key value data size is 128mb.

 

https://wiki.secondlife.com/wiki/LlDataSizeKeyValue

[16:53:33] Object: Total space:  134217728

 

 

 

[Nexii Malthus]

There are many tricks to expand the keystore to fit your needs, you could for example have a naming convention that allows you to figure out/compute the keys on the fly easily. Or you could even store lookup lists in a value to create relationships between other keys, or you could just store full JSON in a value.

You could have a common global key that has a value that stores other keys to lookup. Such as a list of players that are part of a team and then lookup each players information.

Edited August 28 by Nexii Malthus