|HTTP Assets Improve Grid Performance and Other Technology News|
|Geschrieben von: Linden Lab|
|Freitag, den 13. August 2010 um 21:28 Uhr|
It been a summer of major change here at the Lab and I wanted to give you a quick update on how we’re tackling a top priority--platform enhancements that improve grid performance.
An Introduction to HTTP Assets
The HTTP Assets implementation accomplished two important objectives. The first was to move texture requests from a UDP protocol format, to TCP. Using TCP, will increase reliability of proper receipt of those asset requests; UDP is not designed as a reliable messaging protocol and is used where dropping packets is preferred over the need to wait for all packets to arrive. The second was to reduce the need to have the simulator directly managing asset requests. In the past, the simulator would handle all requests from the viewer back into the inventory data bases and asset complex, then back to the viewer. Needless to say, this is not the most efficient or fastest way to deliver those assets to the viewer. Now, the simulator will only be queried to provide a redirect, so that the viewer can fetch the asset directly from a front end web proxy to the asset system servers. Ultimately, the simulator will be completely removed from this path and the viewer will be querying directly to the asset proxy server. If you got a little lost, here’s a visual of what the asset request process now looks like now, in two steps:
OK, So Why Does This Matter?
One More Big Performance Improvement Now Available in Viewer 2.1
I have good news to report. We found and corrected a bug in the latest version of Viewer 2.1. (This particular bug has been present for a while and also exists in the 1.23 code base.) The bug was related to object retrieval, and was causing object requests to bypass the cache and constantly make requests for those objects to the asset system. Generally, most residents frequent the same regions, and the objects in those regions are cached locally so that they can be downloaded very quickly, improving overall rez time. It’s only when objects are changed (not very frequent), or when you visit different regions, that a request for objects are made back to the asset system. So, download Viewer 2.1 and you should notice an appreciable improvement in performance.
More Goodness on the Horizon
My team and I look forward to answering your questions and hearing if you feel the impact of our recent changes.