[sldev] Script/Parcel/Memory Limits - Memory Limit Configuration

[Sheet Spotter]

Using all available prims or all available script/memory may diminish
performance for everyone in the region, even when swapping is not occurring.

 

Most modern operating systems allocate any unused memory for disk or system
cache. Sims that do not use their full prim limit or the maximum
script/memory limit would likely benefit from a larger cache. 

 

When Time Dilation plummets during a lag spike the Net Time, Agent Time, and
Images Time in the Statistics panel seem to spike. Leaving unused memory in
the cache might allow the simulator to handle the spikes in network traffic
or agent updates more easily, or to retain more textures in cache.

 

Admittedly, I'm a performance junky. I never want to use all available RAM.
I always want to ensure unused RAM is available for disk and system cache.

 

Finding a solution that can use all of the available script memory may not
be the best answer. The benefits to using less than the maximum
script/memory limit also need to be considered.

 

 

Sheet Spotter

 

  _____  

From: sldev-bounces at lists.secondlife.com
[mailto:sldev-bounces at lists.secondlife.com] On Behalf Of Cincia Singh
Sent: December 20, 2009 10:55 AM
To: sldev at lists.secondlife.com
Subject: Re: [sldev] Script/Parcel/Memory Limits - Memory Limit
Configuration

 

Just one opinion ... not responding to anyone in particular.

Over commitment of sim resources is what brought us to this conversation in
the first place.
Having a hard parcel limit is how SL avoids over commitment for prims and
it's likely 
the only solution that will work for scripts; both are what we pay tier for.
Just because 
someone leaves a 512 with no prims on it doesn't mean other parcels in the
sim get to 
use them because the sim CAN support their use. Regardless the sim's
capabilities, 
if someone pays tier they should expect that what they pay for stays theirs,
and allocated 
to them, at all times. There is already a way to get more server resource
allocation and 
that is buying more land (server resources).

Coding that allows re-allocation of script resources will eventually cause
lag because 
the elegant coding required to accomplish the re-allocation increases the
likelihood 
someone will find a way to game the system and abuse it.

Ok, now you can rationalize and think up reasons to do it anyway to your
heart's content.
I just had to speak my 0.02L worth.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20091220/d2cc2bdb/attachment.htm