Abdul

Hello everyone!!!

I'm currently designing a server that will collect different kinds of information according to the key of a user. Now, i'm wondering if the function llList2ListStrided() has a limit amount of strides.

What i'm thinking is something like this; "Abdul" "Key of the resident" "date of birth" "Last time online" "Total hours online, hh:mm:ss" "Total amount in L$ collected" "date + time of last collection transaction" "Total amount in L$ donated" "date + time of last donation transaction"

sooooo.....is that too many strides to use in one line? And how much of that information would i be able to fit into one script? Resident wise? ~250?

Thanks in advance, I want to test it out but i would require 250 people to do things on my servers...are there any ways to test all of this out?

Void

there is no theoretical limit to the number of strides, however there is a memory limit...
it should be possible to store the equivalent of ~200 keys safely IIRC.

given the above information, I'd expect ~30 records (assuming that the elements are not actually text but mostly timestamps and other integers) depending on the amount of code being used in the script.

best suggestion is to modify the script slightly so that it duplicates record upwards in batches of 5 testing and reporting the current number is supported.

you may find that separate lists for each field, with each index being a unique record allows you more records, since several functions can duplicate the list in place, effectively doubling it's size while being manipulated. there is a cost in overhead for handling each list separately though and I've never tested whether there's a breakg even point where it becomes better to use one method or the other.

__________________
- These eyes can do more than see

Innula Zenovka

You should be able to save some memory by calculating various fields when you need them. For example, you certainly don't need to store someone's name or date of birth when you have their UUID.

__________________

miranda

If your code ( many functions , and states and events used ) takes 64k , 0 element

It depends too of the repetition of the elements of your list .

This script crashes after 15 000 keys

Without repetition , this script will cras after 600 keys
The elements of the lists can be stored by reference/pointer if they are repetitive .

Nevertheless , when i see the nature of your records , i don t think it will often happen

Of course , i do the hypothesis you compile in MONO ( crash after 160 keys in LSO in the 2 instances )

Abdul

So....it would be safe to say that it would be a better idea to set up an outside server and have it communicate with SL?
I'm thinking something in the lines - have the email send the most resent info and pile it all up in a external server.

Void

in general for a whole bunch of reasons... yes

you can also use llHttpRequest to send post data to a php script, or to query the same external server.... email is a bit slow for LSL

miranda

It depends how your operations on the datas need to be sophisticated .

You may use several scripts to store the datas .
One script plays the role of controler/manager . receives from the world what is the record to append , and communicates with llMessageLinked to the other scripts, to fetch or to append
The other scripts have all the same code between them . It s just a duplication of the same script. Each script keeps a fragment of the datas ( for instance , each scripts keeps in memory 50 records )
So for instance , in your prim you could have in the inventory
- Main script
- data script.1
- data script.2
- data script.3
- data script.4
- data script.5
Inside the llMessageLinked( integer linknum, integer num, string str, key id ) event , the slave script tests , for instance , the num parameter , to know if the message from the main script is for it or for an another slave script