[opensource-dev] Script Memory Limits UI

[Marine Kelley]

This is exactly how I had interpreted it, and this means that a script has
to explicitely request less memory than the default 64k if the scripter
wants to use less memory. And I don't think there will be any other way to
do that than by calling a LSL function to request memory. Which means
modifying existing scripts. This is unacceptable for all well established
business owners who made many different script that are now spread across
SL. To me, a script should take as many bytes as it needs, not more, and
that amount of memory should vary with time. Otherwise it is not
practicable, and will break content once the limits are in place.



On 6 March 2010 21:41, Michael Schlenker <schlenk at uni-oldenburg.de> wrote:

>
> Am 06.03.2010 um 21:25 schrieb Marine Kelley:
>
> > Does that mean we have to modify ALL our scripts to add function calls to
> tailor the memory right, most of the time not even knowing how much is
> needed ? I thought the memory taken by Mono scripts was variable, to a
> maximum of 64k, as opposed to LSL which takes 16k no matter what...
> >
> > If that's the case, if we have to modify all our scripts, after switching
> to Mono (which in itself was a tremendous work because it implied merging
> scripts and updating everything to our customers), then I am sorry to say
> the interest of using Mono over LSL has suddenly gone through the floor.
> >
>
> The comment from Kelly Linden on the blog didn't sound like it, it was more
> like:
> - The default allowed memory footprint of a mono script is 64 kB
> - In the future a mono script will be allowed to request more OR less
> maximum memory for itself
> - IF you know that your script only needs a tiny amount of memory, you can
> set its limit lower to ease the pressure on the sim
>  (which makes it an option for example to use 16 scripts with 4 kB and
> trivial functions instead of one 64 kB script that needs to multiplex
> things)
> - We don't want to break content. Most of the time we cannot guarantee or
> measure the maximum memory usage of a script and to prevent bad effects like
> prims that only work when the phase of the moon is right (aka the garbage
> collector timing) we simply assume a static maximum of 64kB.
>
> I agree on the issue of a horrible UI for the 2.0er memory usage though. It
> should simply sum the number of scripts and show how many LSL and how many
> Mono scripts are involved. The 16kB/64kB details are misleading and useless.
>
> Michael
> _______________________________________________
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/OpenSource-Dev
> Please read the policies before posting to keep unmoderated posting
> privileges
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/opensource-dev/attachments/20100306/b4a3f202/attachment.htm