There is an issue for some with the Mesh Deformer and the time it needs to calculate the mesh for offsetting. Kitsune Shan has been working with the Deformer and voicing concern about the time needed for the Deformer to kick in.
Kitsune is proposing that we do something like what is done with avatar baking. The viewer does the bake and sends a composite image to the servers for everyone else to use. Of course that is being changed to a server side process now, where a new service in servers at the Lab will do the bake and send out the composite image. Kitsune would like to see something similar to that for the Mesh Deformer.
White Rabbit points outthe difficulties with attempting to cache the deformation calculations. White Rabbit has done some testing and finds the CPU time for the Deformer calculation is consistently small. She speculates that the long calc times come from the thread being a low priority process.
The chances that Deformer calc’s will be cached server side is, in my opinion, slim to none. We do not have any statistics on the type of hardware being used with Second Life™. We know there is new stuff, way old hardware, and everything in between. But, AFAIK, we have no information on how much of each.
We have been told that number of users staying with SL Viewer 1.23.x is only 2 or 3%. Third Party Viewers that do not use SSE2 CPU commands is small. Read the SSE2 thing as meaning viewers that support really old computers. Their user bases are so small they fit within the 2-3% too. So, I’ll speculate that the Lab is not going to put much effort into something as complex as caching deformation data.
