Server Releaes Beta : General Discussion

Calib -- Ah. Two different issues that went out together. 1.25.4 had database performance improvement issues in it, but *also* had a lot of other things in it as well, including a scheduler change that turned out to negatively affect script performance. cf: other messages above.

I just announced an aditi database refresh. In there, I say how you can keep your objects through the refresh.

However, I need to ask : how sad would it be if you lost the objects?

Here's the problem : the aditi asset server is filling up. We have to do something about this. The very easiest thing to do is to not only refresh the database, but also refresh all of the simstates on aditi from what's on agni, and to comlpetely clean out the aditi asset server. This would mean the loss of anything you've created on aditi; you'd only have things copied form agni.

Of course, you can keep your scripts by doing cut-and-paste to save them yourself. But you won't keep any objects you've built.

How bad would this be?

Bear in mind that if we have to do a more complicated garbage collection of the aditi asset server, it could be a *lot* of work on our part, is likely to be error-prone, and may not even be feasable. (We routinely run garbage collection on the agni asset servers, but not on the dev grid asset servers, as we assume that we're going to regularly be wiping and refreshing the dev grids.)

Heh, I just assumed the beta grid servers were routinely wiped and refreshed anyway, so I never even bother to create anything there. When did you *stop* doing that?

Something I thought of reading a recent post here...

To avoid "call by value" issues, how about at least allowing non-referencable hashes?

array fred;
fred[1] = "one"
fred[2] = "two"

Instead of passing arrays by reference, you could marshal an array into or out of a 2-strided list.

llSay(0, llList2CSV(fred));
1,one,2,two

fred = ["Argent Stonecutter",0,"Torley Linden",100];
llSay(0,(string)fred["Torley Linden"]);
100

I believe this would not produce any parsing conflicts in any existing legal LSL, since there's no situation I can think of where <<symbol>> <<"[">> is legal.

Prospero, can you parcel off an area and set the flags and announce it here so we can text the fix for SVC-1042?

EDIT: maybe two parcels. One set for Victor's group; Second Life Beta??

Pretty please? I just so happen to have some chocolate chip cookies!


grrrr two dif threads

Somewhere in the 1.25 sequence of code, something got broke. I don't mean a little broke I mean a serious broke.

If you are now in the 'shadow' of a bounding box, you can no longer sit on anything if
(apparently) there isn't an explicit sittarget set for the object.

Try it yourself -

- make a 10x10x.5 platform
- around that make a 10x10x10 cube make it phantom
- stand on the platform and make a normal .5 x .5 x .5 cube

Try to sit on it.
"No room to sit here, try another spot."

without moving or changing anything, hollow the cube completely

You can sit on it easily.

Now, we discovered this a few days ago when suddenly in a few of our buildings, we couldn't sit on certain items. Just certain things. We could before that. All of those items were multisit couches/chairs that worked just fine until this change. After researching it, I found that it was on the land part of some 'floating islands' we had. The base of the islands were 40x40x40 megaprim sculpties, and the 'land' was inside the top 1/2 (40x40x20) of the bounding box of the mega.

Ok, researched the JIRA and found an existing issue on this that had been closed as "Won't Finish" since (apparently) the reporting of this involved mega prims sculpties, same as our problem.

Consulting with a wise, wonderful, witty, charming and intelligent person (puts away smoke blower) I was given the indication that if it could be reproduced with 'normal prims' it could be looked into again.

I came up with the repro above, went to the JIRA, re-opened it, included the repro that did not require megas, sculpties, mega sculpties or sculptie megas (covered all bases there).

It was closed again within minutes as "Won't Finish" (not by the wise, wonderful, witty, charming and intelligent person (this smoke blower is gonna overheat) that gave me the indication, nor by the person that originally closed the issue when it was a sculptie megaprim problem).

So, if you have problems sitting, on something you bought or just a cube this could be the reason why.

Prospero, what Argent said, all the documentation and everything else said has always been that everything on Aditi can and will be wiped at any time with little or no notice and for any reason or no reason at all so not to rely on it for storage so if anyone's using it to store stuff then that's their own damn fault. It's still nice to give them notice but I say wipe it and if anyone loses stuff because of the wipe then let that be a lesson to them for not reading the documentation.

Ilana: what JIRA #?

SVC-3811

I reopened it. I'm frankly tired of people closing things with no explanation. A bug like this isn't excusable.

https://jira.secondlife.com/browse/SVC-3867

what about that..

since the last rolling restart for few days some script don t vanish

looking at the ms tool: world > region/estate tool > debug > get_top_script
the values are 10 times higher & even more than before..
from 500 scripts, and without having changed something now 800 are running..
the ms climbed from 4.1 ms for the whole sim to 50 ms!!

i asked few friends, same at their places..

never saw that before..

&..
weird..
no official statement about that..


i hope it s posted in the right topic, if not please redirect.

have you tried turning off script region wise then restarting it, and then turning scripts back on it may help.... I am thinking this goes in with the ghost scripts bug but I could be wrong

it worked one time..
and now no more..

was nice from 50 ms it was then fresh 3.2 ms for the whole sim..

today it s bad again.. i tried.. and no effect.. badly..
my friends said same.. worked one time only..

Lets give this one a kick because this one should be the active one now, any new build in the preview grid yet or are we still in the test build phase of the next features/fixes?

Lil, where is the new thread for the Beta release on Aditi ??

I haven't been posting Aditi deploys here. Oskar, who manages the Beta group on Aditi, sends messages to the group when new versions are deployed.

Before we have the lights turned off and the door closed: Lil - thank you for being a presence here it is (was) much appreciated.