3000? thats double the amount i would have assumed it is capped at. and yes, the Debug is obviously the preferences setting.
2013/7/26 Darien Caldwell <darien.caldw...@gmail.com> > There has to be some other throttle, because ThrottlebandwidthKBPS seems > to correspond to what you set your bandwidth to in preferences (max 10,000 > with LL's viewer). > > However, This is being capped by the servers: > > 2013-07-26T16:46:00Z INFO: LLViewerThrottleGroup::sendToSim: Sending > throttle settings, total BW 3000.0 > > as you can see to 3000. And it is definitely affecting HTTP, as I can see > the huge slowdown as a result of this 3000 kbps throttle. Textures take as > one would expect 3 times longer to download. (and yes I can handle 10,000 > kbps, having a 25,000 kbps connection.) > > > https://bitbucket.org/lindenlab/viewer-development-materials/src/563d5f7dc77d5de82c310cd60c79560822bde6c8/indra/newview/llviewerthrottle.cpp?at=default > > looking at llViewerThrottle, you can see the 3000 is hard coded as const > F32 MAX_BANDWIDTH = 3000.f; > > > and further down the 'user setting' is clamped to this max: > > //Clamp the bandwidth users can set. > F32 set_bandwidth = llclamp(bandwidth_kbps, MIN_BANDWIDTH, > MAX_BANDWIDTH); > > The throttle has 4 preset 'settings' it dynamically changes between, based > on the Mean packets lost. > > So basically while this system is probably beneficial to those with bad > internet connections, it's rather punitive to those who have excellent, > wide pipe connections. The only way to increase the bandwidth max is to > recompile the viewer. > > > > On Fri, Jul 26, 2013 at 9:54 AM, Niran <desmoulins.u...@googlemail.com>wrote: > >> My Viewer has: >> ThrottleBandwidthKBPS >> which also clearly says this: >> Maximum allowable downstream bandwidth (kilo bits per second) >> >> then theres also this: >> XferThrottle >> Maximum allowable downstream bandwidth for asset transfers (bits per >> second) >> >> so i guess asset and everything else is also split, at least if this >> Debug is really used, it has no HTTP Debug which makes me assume that HTTP >> is free from a limit at least clientside...or its hardcoded...but back to >> the question, according to the Debug string its kilobits. >> >> >> 2013/7/26 Carlo Wood <ca...@alinoe.com> >> >>> On Fri, 26 Jul 2013 13:58:47 +0200 >>> Henri Beauchamp <sl...@free.fr> wrote: >>> >>> > This setting is indeed only relevant to UDP traffic, or at least in >>> > LL's and most TPV viewers. IIRC, I saw attempts to account for this >>> > limit with HTTP texture fetching traffic in Singularity, but that >>> > would need to be checked for certainty. >>> >>> Singularity has a separate debug setting for HTTP bandwidth usage >>> (HTTPThrottleBandwidth). >>> >>> -- >>> Carlo Wood <ca...@alinoe.com> >>> _______________________________________________ >>> 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 >>> >> >> >> _______________________________________________ >> 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 >> > > > _______________________________________________ > 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 >
_______________________________________________ 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