On 10/22/2012 6:28 PM, Henri Beauchamp wrote: > In the current implementation, the new HTTP core can be configured to > spawn from 12 to up to 256 (!) simultaneous connections... The texture > fetcher code however never queues more than 40 requests at once, thus > limiting the potential damages, but you might want to have a look at > that and provide safer bounds before the new HTTP core gets used for > more services in the viewer...
No, the current HTTP code allows up to 12 concurrent connections with a shipping default of 8. A debug control is available to *reduce* not increase the concurrency. I'm interested in having available a control more refined than HTTP Textures on/off for people who have chronic connectivity problems. My hope is that knocking back concurrency will prevent certain routers from falling over. But other consumers, like mesh fetch, may completely swamp any improvement that control might offer. > My backports allows from 8 to 32 simultaneous connections, with 12 as > the default (i.e. same default as in viewer-http). You're running 50% hotter than I am. Stop eating all the sockets! :-) m _______________________________________________ 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
