Sever Deployments for Week 12
Second Life Server (SLS)
On Tuesday March 19th, the Main channel received the server maintenance package which had been re-deployed to Magnum in week 11. As with the Magnum re-deploy, it excludes the fix for VWR-786 while LL go “back to the drawing board” to try to correct issues. However, it does include the following two fixes:
- BUG-1612: region Owners and estate managers finding they are unable to teleport back to their region after disabling direct teleports to the region
- SVC-8019: region visibility delays following region restarts.
The release notes for the deployment are available on the SL wiki, as usual.
Release Candidate Channels
On Wednesday March 20th, the Release Candidate channels should receive the following updates:
- BlueSteel and LeTigre: should receive the same updates as deployed to the SLS channel on Tuesday March 19th, but otherwise retain the same updates received in week 11 – release notes (BlueSteel)
- Magnum: should receive further updates to Andrew Linden’s interest list work, as per the release notes. Specific interest list bug fixes included with this update comprise:
- Updates for objects that are out of view are delayed for a maximum of 5 seconds, at which point they will be sent (mitigates BUG-1779)
- Fix for “No object updates from vehicles after some region crossings” (BUG-1814)
- Fix for “Agent appears in incorrect position to other agents after being moved by a sim teleporter” (BUG-1795).
As reported in week 11, the second official Server-side Baking pile-on / load test appeared to go well on Thursday March 14th. Speaking at the Content Creator’s User Group meeting, SSB project lead Nyx Linden reported:
Looks like things are going well overall – the back-end services are performing well. There are still some inventory and attachment rezzing issues, but these are believed to not be regressions from current limits.
A few reports of issues, some of which we have fixes for, others we’re investigating, and we’re looking at what it would take to fix up the systems that were falling over … there were a couple of new bug reports we’re investigating.
A further SSB pile-on / load test conducted in Friday 15th March, but exclusively with the Firestorm viewer pre-release with SSB support. Numbers at the Firestorm test were roughly the same as those for the “official” test, and overall, the outcome was the same – much lower reported SSB issues, but similar problems with outfit attachments rezzing from inventory (or rather, failing to), which was common to both parts of the test.
The inventory issues have themselves become more of a focus of investigation outside of SSB itself (attachments aren’t affected by the SSB code changes, which relate directly to the likes of skin, shape and clothing layer changes. While the inventory issues were thought to relate solely to Aditi, Nyx indicated that the problem is likely common to Agni as well. commenting:
We were seeing similar failures in inventory, etc on both the old pipeline and the new pipeline, and in areas that we didn’t change. So if we repeated the test on Agni we think we’d see similar failures. We’re looking at the root causes, but attachment rezzing failures won’t necessarily block our first release … We’re looking at the inventory & attachment issues and where their root causes are.
Expect further updates on the latter issue as they become known.
All of the test regions for Monty Linden’s upcoming HTTP updates are now up-and-running on Aditi, and available for public access (allowing for the caps on avatars in the primary test regions). The regions are:
- DRTSIM-203 (Agni default settings): TextureTest2, MeshTest2, and Sandbox HTTP
- DRTSIM-203H (the “Happy” channel): TextureTest2H, MeshTest2H, Sandbox HTTP H
- DRTSIM-203A (the “Angry”) channel): TextureTest2A, MeshTest2A, Sandbox HTTP A.
As noted in previous project reports, Monty is keep to have TPVs and scripters test the capabilities in order to gather more comprehensive data on his work.