I believe the 2 persistent HTTP connections/server recommendation is just
that: a maximum of 2 *persistent* connections *per server*. Torrent
downloads are more likely 1 connection per server with many servers.
Torrent clients also have the ability for users to specify maximum outbound
transfer rat
On Tue, 23 Oct 2012 10:28:37 -0400, Monty Brandenberg wrote:
> Here's a chart I keep forwarding:
> http://www.smallnetbuilder.com/lanwan/router-charts/bar/77-max-simul-conn
> Not officially endorsed by Linden, etc., but a useful measure of
> one metric that is likely to predict problems. At the b
On Tue, 23 Oct 2012 11:05:38 -0700, Dahlia Trimble wrote:
> Would this excerpt from RFC2616 (section 8.2) be relevent? Perhaps some
> routers and other infrastructure assume this as design criteria:
>
> " Clients that use persistent connections SHOULD limit the number of
>simultaneous conne
On 2012-10-23 15:25 , Monty Brandenberg wrote:
On 10/23/2012 2:05 PM, Dahlia Trimble wrote:
Would this excerpt from RFC2616 (section 8.2) be relevent? Perhaps some
routers and other infrastructure assume this as design criteria:
Oh, it absolutely is but mostly honored in its breach. IETF 'SHO
On 10/23/2012 2:05 PM, Dahlia Trimble wrote:
> Would this excerpt from RFC2616 (section 8.2) be relevent? Perhaps some
> routers and other infrastructure assume this as design criteria:
Oh, it absolutely is but mostly honored in its breach. IETF 'SHOULD'
is so much weaker than its 'MUST'
_
On 2012-10-23 14:05 , Dahlia Trimble wrote:
> Would this excerpt from RFC2616 (section 8.2) be relevent? Perhaps
> some routers and other infrastructure assume this as design criteria:
> "
> Clients that use persistent connections SHOULD limit the number of
> simultaneous connections that
Would this excerpt from RFC2616 (section 8.2) be relevent? Perhaps some
routers and other infrastructure assume this as design criteria:
"
Clients that use persistent connections SHOULD limit the number of
simultaneous connections that they maintain to a given server. A
single-user clien
On 10/23/2012 6:10 AM, Henri Beauchamp wrote:
> And in fact, llappcorehttp.cpp only touches CP_CONNECTION_LIMIT, so
> CP_PER_HOST_CONNECTION_LIMIT is kept at its default (8) whatever the
> TextureFetchConcurrency debug setting value, meaning the viewer never
> opens more than 8 simultaneous connec
On 2012-10-23 06:10 , Henri Beauchamp wrote:
> Unless the router is buggy, it shouldn't be impacted by the number of
> open sockets (at least not under 60K sockets)... Some protocols, such
> as torrent can use hundreds or even thousands of sockets at once.
Our experience is that _many_ consumer ro
On Tue, 23 Oct 2012 00:01:29 -0400, Monty Brandenberg wrote:
> 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
10 matches
Mail list logo
