On 7/30/2013 11:39 PM, Ambrosia wrote: > Additionally to that, the amount of traffic that goes through the > actual sim these days has been highly reduced with bringing > textures, mesh and materials onto the sim-external HTTP pipeline > that isn't bound to a single sim.
CAPs are per sim host I believe, so flooding requests on them could affect a number of regions and not just the one the agent is connected to. > Of course there is still people who feverishly set their texture > pipeline to UDP because that's what they did a year ago when the > HTTP pipeline was less mature. One of those people has more impact > on the performance on sim-entry than any person with a 3k bandwidth > setting, but HTTP-enabled texture pipeline, will ever cause these > days. Remember when HTTP textures was first added and it was really really much faster than UDP? Remember when HTTP texture CAP use became mainstream on 99% of agents and how it became almost as slow as UDP was? And if you have a crappy consumer router (like it sounds like Niran has), you can end up with pretty sever issues from it choking on all the quick successive connections the viewer makes. Monty's work HTTP on both ends will have (has had) great improvements here. _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
