Jump to content

Deploy Plans for the week of 2019-10-21


You are about to reply to a thread that has been inactive for 607 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

Note: https://releasenotes.secondlife.com/simulator/2019-10-03T01%3A12%3A11.531528.html goes everywhere

 

Second Life Server:
https://releasenotes.secondlife.com/simulator/2019-10-03T01%3A12%3A11.531528.html

Second Life RCs:
https://releasenotes.secondlife.com/simulator/2019-10-03T01%3A12%3A11.531528.html

Scheduled Wednesday 2019-10-23 07:00-10:30 PST

 

On Region Restarts:

Regions will be restarted if they have been running for more than 10 days on Tuesday (Main Channel) and Wednesday (RCs) regardless of whether or not new code is being deployed, for the general health and well being of the Simulators. Nothing beats turning it off and then on again ... once in a while.

As always please plan events around these maintenance windows. However, if you are hosting an event on Tuesday or Wednesday when we're not deploying new code, you can restart your region ahead of time to avoid interruptions.

  • Thanks 6
Link to post
Share on other sites

Interesting. In long-term observations, we noted a positive stabilization and, consequently, an increase in script performance, which had more than a positive effect on the regional performance. From us, the last week rolled version could remain. And my wife and I know our regions only too well and know the performance to judge it.

With the todays DOWNGRADE we lost more than 50% of the Scriptperformance we had before with 531693. Is that the will of Linden to keep us on low Level?

Edited by Miller Thor
  • Confused 1
  • Sad 1
Link to post
Share on other sites
2 hours ago, Miller Thor said:

With the todays DOWNGRADE we lost more than 50% of the Scriptperformance we had before with 531693.

That's way too much. I've been watching script performance for a number of Mainland regions the past few months and have seen only single-digit increases in Scripts Run percentages with the recent script improvements. That may be all we should expect at this point because they've only really affected listen() and sensor() events -- there's been no attempt yet to address the elephant in the room: inefficient impact of idle scripts on scheduler performance.

That said, though, I too have seen a region's script performance dip by 50% with one restart and restore to the previous high level with the next even when all three conditions were on the very same release. This happens at random, as far as I can tell. If you can arrange a restart for your region it may be a magic cure -- until the next unlucky restart, and there's no telling how many attempts it takes to get a good host -- but it may be worth a try.

  • Thanks 4
Link to post
Share on other sites
You are about to reply to a thread that has been inactive for 607 days.

Please take a moment to consider if this thread is worth bumping.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...