Re: [opensource-dev] Script Memory Limits UI

I don't think that dynamic memory would be hard to implement, but problem is that avatar/parcel have (or is going to have) limited memory available. 1) It is not possible swap memory to server's hard drive - because that would cause lag - and is actually reason behind why memory limits are com

Re: [opensource-dev] Script Memory Limits UI

It's not impossible... it's actually rather simple. That being said, I wouldn't be surprised if LL feels it's too difficult for them. [ I suppose remarks like this (that it is simple) have usually not got any weight, therefore I already added the fact that I wrote a malloc library myself in the p

Re: [opensource-dev] Script Memory Limits UI

That's right. Computer programs are constantly managing two contradictory resources, space and time. In theory we need control over script time as much (no more no less) as we need control over script memory. But let's not ask for even more additional workload than we already have. On 9

Re: [opensource-dev] Script Memory Limits UI

> So, cool, wouldn't it be nice to only allocate what is actually > requested? That -is- in the works, with the Small Scripts and Big Scripts projects. it will allows you to reserve just as much memory as you need for mono scripts, less than the 64k..or even more. But alas, yes, time will have to

Re: [opensource-dev] Script Memory Limits UI

Change requires work. Unnecessary, unwanted, and uncalled for in this instance. We have to adapt to handle a part of the task that LL was supposed to do themselves. Oh of course this is a hard job, allocating memory dynamically in an environment like this. Perhaps it is impossible. I have y

Re: [opensource-dev] Script Memory Limits UI

On Mon, Mar 8, 2010 at 8:40 PM, Lear Cale wrote: > It would be nice if everything were free, too... > Until now, script memory has seemed to be a free lunch.  Well, the > free lunch is over, and we'll have to deal with it. I wouldn't mind "dealing with" lunch not being free if a crappy bloated sc

Re: [opensource-dev] Script Memory Limits UI

On 2010-03-08, at 19:41, Lear Cale wrote: > Babbage has already said that LSO code will be "charged" 64K even > though it only uses 16K. Perhaps he's changed that decision -- is > that the case? I'd like some clarification there too, because I read that they'd backed down on that idea (which is

Re: [opensource-dev] Script Memory Limits UI

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What if the memory allocation worked kinda like those bouncing bars on top of those audiofrquency/spectrum/VUmeter readouts on some stereos and many computer audio players, where it's fast to go up, but then it falls slowly back till it hits the curren

Re: [opensource-dev] Script Memory Limits UI

It used to be that simple, with original LSO. With mono, it's more complicated, because two instances of the *exact* same script can share the code segments. I wonder whether this sharing ability will be taken into account. Ideally yes, because it's best when the metrics used to measure somethin

Re: [opensource-dev] Script Memory Limits UI

Babbage has already said that LSO code will be "charged" 64K even though it only uses 16K. Perhaps he's changed that decision -- is that the case? Regards Jeff On Sat, Mar 6, 2010 at 9:02 PM, Frans wrote: > In response to the OP. I agree the UI will have to present that information > differentl

Re: [opensource-dev] Script Memory Limits UI

It would be nice if everything were free, too. The issue is memory *allocation*. If a script only uses 16K but is allocated 64K, that 64K counts against the server's actual memory allocation limit. So, cool, wouldn't it be nice to only allocate what is actually requested? Well that implies rewr

Re: [opensource-dev] Script Memory Limits UI

On 2010-03-06, at 20:02, Frans wrote: > In response to the OP. I agree the UI will have to present that > information differently. As it is now people will merely make a > decision on memory usage and choose LSL scripts, and remove mono > scripts. Likely negatively impacting their own experie

Re: [opensource-dev] Script Memory Limits UI

As far as I understand it a script (the item you manipulate in-world) is a bytecode (a compiled version of your code without the comments, the spaces and the returns) loaded into the sim, plus its simple, constant-size variables (integer, floats), all of which forming the stack. Then you have all t

Re: [opensource-dev] Script Memory Limits UI

May I ask a probably dumb question here? It's probably been answered but I can't find the answer now. Presumably a script uses two resources, the byte code in its assembly and a slab of memory allocated for its stack/heap. And am I right that the former can be shared between multiple copies of a

Re: [opensource-dev] Script Memory Limits UI

I agree completely, Marine. We're being given a choice of two options which together make no sense, and worse, represent an undue burden on scripters and a regression into the distant history of Computing. The system should define a *large* but *hard* limit to the maximum memory allocated per scr

Re: [opensource-dev] Script Memory Limits UI

Well we have two mutually exclusive solutions here. Either Mono scripts are given a hard memory limit that we (the scripters) can change within the scripts, with all the overhead work that it implies (i.e. modifying hundreds of scripts before issuing an update, and having to know upfront how much

Re: [opensource-dev] Script Memory Limits UI

In response to the OP. I agree the UI will have to present that information differently. As it is now people will merely make a decision on memory usage and choose LSL scripts, and remove mono scripts. Likely negatively impacting their own experience. Scripters will be driven to compile scripts as

Re: [opensource-dev] Script Memory Limits UI

On Sat, 6 Mar 2010 20:49:35 + Morgaine wrote: > You have to be joking. (Or rather, Kelly has to be joking.) > > It's been decades since computer users last had to specify the memory > requirements of their programs in advance of running them. > > Has 1970 returned again? This is progress?

Re: [opensource-dev] Script Memory Limits UI

On Sat, Mar 06, 2010 at 09:51:49PM +0100, Marine Kelley wrote: > 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

Re: [opensource-dev] Script Memory Limits UI

On 2010-03-06, at 14:49, Morgaine wrote: > It's been decades since computer users last had to specify the > memory requirements of their programs in advance of running them. About a decade. Mac OS required you to specify the partition size required by your program. This was also pretty common

Re: [opensource-dev] Script Memory Limits UI

Oh! And read the Kelly's comments in https://blogs.secondlife.com/community/technology/blog/2010/03/05/server-138 -beta-now-open : "Right now there is no way to change how much memory a mono script uses,

Re: [opensource-dev] Script Memory Limits UI

ning any time soon. GCI - Original Message - From: Morgaine To: Garmin Kawaguichi Cc: Matt White ; opensource-dev@lists.secondlife.com Sent: Saturday, March 06, 2010 9:49 PM Subject: Re: [opensource-dev] Script Memory Limits UI You have to be joking. (Or rathe

Re: [opensource-dev] Script Memory Limits UI

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 modifyi

Re: [opensource-dev] Script Memory Limits UI

You have to be joking. (Or rather, Kelly has to be joking.) It's been decades since computer users last had to specify the memory requirements of their programs in advance of running them. Has 1970 returned again? This is progress? Morgaine. On Sat, Mar 6,

Re: [opensource-dev] Script Memory Limits UI

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 oppos

Re: [opensource-dev] Script Memory Limits UI

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

Re: [opensource-dev] Script Memory Limits UI

Oh! And read the Kelly's comments in https://blogs.secondlife.com/community/technology/blog/2010/03/05/server-138-beta-now-open : "Right now there is no way to change how much memory a mono script uses, and it is true that at any given point it probably uses less than 64k, by some amount. How

Re: [opensource-dev] Script Memory Limits UI

Try with this mailing list, it's more approriate! https://lists.secondlife.com/cgi-bin/mailman/listinfo/server-beta GCI - Original Message - From: "Matt White" To: Sent: Saturday, March 06, 2010 5:21 PM Subject: [opensource-dev] Script Memory Limits UI