[opensource-dev] Script Memory Limits UI

Matt White mwhite at leporidae.net
Sat Mar 6 08:21:16 PST 2010


Hello!

I've attached a screen shot of the new Script Information screen that
you can see when you log into the beta 1.38 server with the SL2
client.

Linden Lab - I'm begging you.. *PLEASE* do not push this feature out
to the main grid until Mono scripts are actually charged what they
use. Please, please, please!

This screen shot shows exactly what's wrong - I have some attachments
with very simple scripts in them (just a couple of lines of LSL with a
very tight listen), but they are charged a full 64k. I don't need for
the scripts to be Mono - they work great with LSL - but I compiled
them as Mono because "it was the right thing to do", and now that's
coming back to bite me.

I take great pride in making sure my scripts are as tight on resources
as I possibly can, and none of this is taken into account. A two
script item that's compiled as LSL is going to be charged *HALF* as
much as a very simple Mono script, even if the Mono script is just one
line and the LSL scripts are 16k and pushing the limit memory usage.

We listened to you - we moved from LSL to Mono. Now it seems that was
a foolish move.

I predict this feature is going to have exactly the opposite effect
intended - it's going to force everyone to go back to LSL and way from
Mono. (As if we needed another reason besides the several second
pauses every time a script-heavy AV TPs in.)


We're geeks. We can understand the difference in 64k on Mono and 16k
on LSL, but the average SL user does not. This feature, as it's
implemented right now, does not help matters. All it shows is "just a
number" with no indication as to how much memory is actually in use
and if the script is LSL or Mono. Anyone can see that 64 > 16, so 16
must be better. Four times better.

I know the plan is to not start ENFORCING memory limits until Mono
scripts are charged what they use, but I'm scared it won't matter much
- people are going to migrate away from Mono and back to LSL given the
way this screen looks today.

Please consider reworking how this screen looks. Add an "in use"
column or make LSL and Mono be treated fairly... but please don't push
this live as-is!

- Matt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: memoryLimits.jpg
Type: image/jpeg
Size: 39412 bytes
Desc: not available
Url : http://lists.secondlife.com/pipermail/opensource-dev/attachments/20100306/ea3dab80/attachment-0001.jpg 


More information about the opensource-dev mailing list