Khamon Fate
fategardens.net
Join date: 21 Nov 2003
Posts: 4,177
|
04-12-2006 05:45
I wonder if LL will publish a rough estimate of system resource usage devoted to such features as traffic calculations and payments. Without arguing the initial goals of dwell, and the varying implementation strategies of social engineering techniques, I'd just like for the population to see some raw numbers so that we can provide some intelligent feedback.
It's either not much of a drain on the system, or it dents our world's performance noticably. Nobody will care if the former is true. Proving the latter might generate some intelligent feedback from us to you.
Is LL even interested in the population's general opinion of feature sets based partly on our knowledge of resource usage? I may be just be assuming something about y'all. Wouldn't that be a turnabout hoot.
_____________________
Visit the Fate Gardens Website @ fategardens.net
|
Kelly Linden
Linden Developer
Join date: 29 Mar 2004
Posts: 896
|
04-13-2006 14:09
I do not believe any in depth analysis has been done on the performance cost of dwell.
I am not a master of the Dwell code, however a quick perusal shows the following: Each simulator tracks the dwell as time agents spend within each of its own parcels. This is extremely light weight resource wise, and the only real load incurred on the simulators. Cumulative dwell is recorded on a regular basis, at the same time as many other necessary stats and thus incurs essentially no overhead beyond what would happen without it. The daily numbers are calculated and updated in a completely seperate script, and thus also has essentially no performance impact.
I do not know the answer to your last query. While we have received valuable performance analysis from residents in the past, given the currently opaque nature of our system it is rare. Many performance issues simply are not diagnosable without directly inspecting the code, and the intersecting nature of Second Life features means there are many, many red herrings - even when looking directly at the code.
_____________________
- Kelly Linden
|