#SecondLife Server Updates Week 24.5

The week of 6/12-18 there was not a main server roll out. The week of 6/19-25 we did get a roll out on the main grid. The roll out had the group chat fixes.

Group Chat

Group chat has been receiving attention. The Utility Servers were updated over a week ago. Now the region simulators are updated, a minor fix.

One of the Group Chat Problems found was the Utility Server for chat had to send chat messages to multiple people in a region. If ten people were in a region the server had to send ten copies of chat updates to the region. This change allows the utility server to send the sim one message and the simulator distributes the chat updates. This sim change is not something that makes a lot of difference to most users. But, any load taken off the utility servers running group chat helps.

The previous update to the utility servers has made a significant difference to group chat for everyone. Enough so that this alarming JIRA was filed: https://jira.secondlife.com/browse/SVC-7031

Group Chat Performance

The above image is a plot of chat messages (messages + group status updates) per minute sampled over one day. Each dot is one of the 16 utility nodes.

Read more

#SL Chat Update

You probably remember that on the first of the month I posted Second Life Chat Load Test. That test was carried out last week. It was hoped we would see some of the numbers this week. That didn’t happen but we did get some of the story from Oskar Linden in the Beta Server Group meeting. I also posted #SL Server Follow Up Week 23, which has a section on chat. That article explains the inefficiencies in group chat.

The Test

Three regions were involved. One running the main grid server-trunk version (Oatmeal ) and the other two running the a test version with improved chat software. Also, the Utility Servers received new software weeks prior to the test. Nobody told me. But, Oskar just officially announced it here: UTIL hosts updated with Group Chat fixes.  The test was pretty well covered in blogs, forum, and group notices. The turnout was good and the Lindens collected lots of good stuff… data. Oskar Linden said, “It was a huge success from a QA POV.”

The main things being tested were backward compatibility – old grid software to new grid software, multi-region chats, and large in region group chats.

Read more

#SL Server Follow Up Week 23

The meeting notes from the Beta Server Group came out. There is some interesting stuff from the meeting. We got great information on CHAT. 🙂

Server Stability

The Lab has been working on what is labeled Server-Maint. This is a group of fixes and features that allow better roll out and problem recoveries. It has taken several tries and roll outs from the Release Channel had to be rolled back each time. The problems seems to have passed and Server-Maint. has made it to the main grid.

Mono2

This upgrade has been cycling through the Release Channel for 3 or 4 weeks now. This changes touches so many aspects of SL that it is a complex change. While performance of new scripts rezzing in a region has been greatly improved, avatars with hundreds of scripts are still a problem. The Lab was working on that last week and the new fixes are in testing on Le Tigre this week. If they prove up, they will make the main grid next week.

Read more

Second Life Server Updates Week 23

Today we are getting new roll outs to the main grid and tomorrow release channels. There have been problems with recent releases for 3 or 4 weeks. Projects were rolled back, revised and retested on the release channels. Code for the introduction of mesh has and is being merged into the main code base during this time. It seems this has revealed a rash of problems that are being fixed. The result is the news about server upgrades is rather boring and vague.

Main Grid – AGNI

The changes rolling to the main grid are mostly what I’ll call backend changes, those we don’t really see. They affect our experience in terms of performance. But, there is nothing new like shadows or Display Names to see.

This release has the ever ubiquitous bug fixes.

The API (Application Programming Interface) for working with friends changes.  This is something those building applications for Second Life and viewers can make use of. For the rest of us, it has little relevance until others implement the use of it.

Read more

#SL Server Updates Week 20

The last two weeks have been hectic for the Lindens. Several updates to the server software did not work as expected and the crash rates went up. It seems those have been corrected and things are returning to the normal cycle of upgrades.

This week’s (today’s) roll out was stopped and rolled back part way through the process. Something went wrong.

Server Room
CERN Server Room - By: torkildr @ Flickr

Snack Release Channel

One of the code updates that is proving difficult to get working is the Mono2 upgrade. You probably remember it is the Mono scripts rezzing in a region that caused regions to stall for 5 to 30 seconds. That fix has been in progress since Mono was released. A couple of times now Mono2 updates and improvements have been rolled out and back. The Snack Release Channel is a special channel made up of just a few simulators on the main grid where the Mono2 changes can be tested.

Read more

Server Updates Week 18

Not much exciting stuff this week. There is some confusion as to what is happening. If I understand correctly the Maint-Server updates are still in the Blue Steel channel and they have been rolled to the main grid. The updates are a collection of fixes to known problems, a couple of bugs that crash sims and a logging thing that should help performance have been added to Blue Steel and will now be testing.

A little disappointing is the fix for jumping vehicles, the bounce as they move from prim to prim, which in testing on the ADITI grid has been removed. The fix worked with Havok 4 (which was on the main grid in mid 2010) but has been shown to create unexpected side effects with Havok 7 in ADITI. See JIRA SVC-5880 for the history of this fix. So, the lab will backup and try again.

Read more