I'll be honest. I just really don't like the dynamic resource limits idea. It is very neat and interesting in theory, and fun to design and discuss. However I see a lot of value in knowing all my content will continue to work and knowing what content I can use - In knowing that when I buy/rent/lease land as part of that I am buying/renting/leasing a specific amount of resources. I hate the idea of *any* of my content only sometimes working.
I place a high value on simplicity. I want to trivially understand where I am, how much headroom I have, how close I am to what limits there are. I don't want to code complex solutions with multiple behaviors based on the state of the region. And yes, I know people already do this by monitoring sim stats but it would be awesome if they didn't need to. "normal" residents also need to understand these limits and be able to see where they are. These limits will effect *everyone*, even if all you do is rent a house and buy content to furnish it. You will need to know what will and won't work and buying something that will sometimes work no matter what the reasons is just going to be a nightmare. If I buy a fish tank it needs to always work and always have fish and not have fish that sleep or disappear when my neighbors decide it is chicken shooting time. That said, I also understand the usage issues here, which mirror closely the more generic web hosting problems. Resource usage patterns aren't equal or consistent over time or space, this is obvious and known and is NOT something we are ignoring. The general solution for web hosting is to over-sell, rely on some rules of averages and be able to move things around to accommodate users. Doing something similar is certainly a possibility, and one I have pushed for. It isn't as trivial as just setting higher numbers - we need to adjust and fix our infrastructure to more optimally assign regions to hosts - but it is certainly not impossible, and indeed such infrastructure changes would benefit everyone regardless. Dynamic resource limits are just complicated by nature. They are fluid in some respect, and they change based on time and usage - that is just what it means. Unfortunately it is that nature that makes it hard to plan around and hard to build content for and hard to understand. The system we use needs to be as easy as prim limits are now, where you can see the cost of an object and you can see how much you can support. - Kelly On Fri, Dec 18, 2009 at 9:13 AM, Da5id Kronfeld <da5idkronf...@gmail.com>wrote: > > On 2009-12-18, at 4:10 AM, Aleric Inglewood wrote: > > > On Fri, Dec 18, 2009 at 05:52:26AM -0600, Argent Stonecutter wrote: > >> If the sim as a whole is over 75% of the limit, all parcels would be > >> restricted to strict limits. > > > > That is instable, you shouldn't shift the limit in a way that > > it can start oscillating. Also, it won't solve my problem with > > the "chick-shoot game": > > [cut] > > > Your solution doesn't work either however: In your case I would > > start rezzing chickens, and when I rez chicken 76, suddenly > > the limits would kick in full force and 66 chickens would die, > > only leaving 10 to run free. At that moment we'd be under the > > 75% again though, so my chicken rez object would start creating > > new chickens again, until it again rezzes the 76th chicken... > > While I'm still on the fence about dynamic limits, this oscillating effect > can be mitigated by damping factor that doesn't allow the sim to return to > an overcommitted state immediately following a script cull. > _______________________________________________ > Policies and (un)subscribe information available here: > http://wiki.secondlife.com/wiki/SLDev > Please read the policies before posting to keep unmoderated posting > privileges >
_______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/SLDev Please read the policies before posting to keep unmoderated posting privileges
