Got memory-intensive scripts? Time to visit beta grid for a stress test.

Forwarding some info from the secondlifescripters list, since not everyone is on that.

On the aditi grid, there are two regions Scheduler Test 2 and Scheduler Test 3 that have, like the name implies, a new version of the mono runtime with the updated scheduler code that was pulled from early 1.25 and since reworked.

Manipulations on large lists that relied on a current scheduler bug to fit in memory will hit their real limits under this new scheduler, and will break. so you'll want to find out about this borkage before it comes to the main grid.

For the full announcement:

https://lists.secondlife.com/pipermail/secondlifescripters/attachments/20090320/1bc5c324/attachment.htm

ETA: That HTML is rendering as plain text so it's a little hard to read. Periapse also did a much more readable wiki page covering the details:

http://wiki.secondlife.com/wiki/Mono_Scheduler_testing

Thanks.

Thanks, Viktoria, you beat me to it. Here's the text of my list email:

Studio Blighty is reworking the Mono Scheduler, the simulator module which manages the allocation of resources (cpu, memory) to all the scripts running in a region. This is necessary because the original scheduler's behavior was unpredictable; it allowed some scripts to hog resources at the expense of other scripts and to the detriment of overall region performance.

Tuning the scheduler is tricky work since its job is to make tradeoffs of script performance vs region performance. We have a new Mono Scheduler which passes our internal benchmarks, and we'd like some feedback on how it performs against real LSL scripts.

Attention deficit version:
* Do you write Mono LSL scripts with either large lists, or use lots of memory or calculation?
* Then go to aditi to test your scripts in one of these regions: Scheduler Test 2, 3, or TG (for Teen Grid).
* Comment on https://jira.secondlife.com/browse/SVC-3997 if you have feedback.

Slow-down-and-start-from-the-beginning version:
* The original Mono scheduler was essentially non-deterministic. Certain "lucky" scripts were able to hog resources and impair performance of other scripts and bog down the overall region performance.
* The Scheduler needs to be strict enough so as to maintain region performance while still delivering acceptable script processing speeds.
* Studio Blighty generated some reasonable benchmarks, and crafted a reworked scheduler which delivers them.
* Benchmarks are not a substitute for real world scripts (ahem, I guess I mean real world virtual world scripts).
* We've deployed a special simulator version to a couple of regions on aditi, the preview grid. This simulator contains the new Mono Scheduler.
* There are two sandbox regions on aditi for adult residents: Scheduler Test 2 and 3.
* Our teen scripters can test their work in Scheduler Test TG.
* If you have a script which runs fine on agni, but which runs out of memory on these test regions, please note it in https://jira.secondlife.com/browse/SVC-3997.
* Use that JIRA also if you find significant performance degradation between the main grid and the test regions.
* For detailed instructions see the wiki: https://wiki.secondlife.com/wiki/Mono_Scheduler_testing

How do I login to the beta test grid ?

I've selected 'Aditi', from the dropdown, the Beta Test Grid splashscreen appears, when I use my regular login/pw, it says Login failed .. check right account, password.

works fine for me, unfortunately my isp still has me hamstrung so I can't actually accomplish much. =/

When I used Beta a while ago, the same thing happened to me; it turned out that I had recently changed my password for the reg viewer and the beta was using my old password. Maybe its that?

Your avatar is very new, so the preview database won't know about you yet. They refresh it manually every few months.

"months" ?

That's like centuries in computer time

... Or at least years in dial-up time