Server Deployments Week #29 – Recap
As always, please refer to the server deployment thread for the latest updates / news.
- There was no Main (SLS) channel deployment on Tuesday, July 14th.
- On Wednesday, July 15th all three RC channels received the same server maintenance package, comprising internal simulator fixes.
Following the promotion of the attachment fixes viewer to release status, all three remain active release candidate viewer in the release channel were updated as follows:
- The Viewer-Managed Marketplace RC viewer updated to version 126.96.36.1993583 on Thursday, July 16th
- The Maintenance RC viewer updated to version 188.8.131.523563 on Friday, July 17th
- The Mesh importer RC viewer updates to version 184.108.40.2063565, also on Friday, July 17th.
On Thursday, July 16th, the Lab announced that VMM is now “released” (even through the viewer is currently still at RC status), and that automated migration of those Marketplace stores which have not already converted to VMM will commence at 21:00 SLT on Thursday, July 23rd, and will continue at the same time on weekdays for a 12-hour period (21:00 – 09:00) until complete.
That the announcement has been made prior to the viewer being promoted, and that it was made apparently without any notification to TPVs (who had been trying to work closely with the Lab in getting people ready for VMM) has caused no small amount of upset on the Commerce forum thread opened when the announcement was made, some of which is understandable, particularly given the way TPVs have tried to work with the Lab in support of VMM, and this announcement have left those still in the process of trying integrate the code into their viewers with little time to actually do so and support their users with a VMM-enabled version of their viewer.
In my week #28 report, I referred to a comment made by Simon Linden relating to Experience Keys / Tools concerning some work he’s been carrying out on the KVP database:
I’ve been working on updating the KVP code that runs on our server and had the most frustrating time integrating the newest version into our code … The code we have is dated and we should have better performance and stability with their latest.
The use of “their” and “our” code led to some questions at the meeting (unanswered at the time) as to what it might indicate. During the Server Beta User Group (SBUG) meeting on Thursday, July 16th, some clarification was given.
The “their” referred to by Simon is MongoDB, which is the database being used to manage the KVP store and key value pairs. The version the Lab had been / is using can only apparently search around 1,000 values per minute. The new version that Simon has been working on should apparently improve on this, hence his reference to performance and stability improvements (not to mention scalability).