Gentoo Archives: gentoo-user

From: Michael Mol <mikemol@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] I/net server throttling
Date: Mon, 02 Jul 2012 03:13:11
Message-Id: CA+czFiDNnp_sh-0iHHxwB7c2NUndht=c4Zy6NtUpmJb028rvRg@mail.gmail.com
In Reply to: Re: [gentoo-user] I/net server throttling by Philip Webb
1 On Sun, Jul 1, 2012 at 8:26 PM, Philip Webb <purslow@××××××××.net> wrote:
2 > 120701 Michael Mol wrote:
3 >> It could be a connection duration limit.
4 >> Either the web server or an intermediate proxy server
5 >> may place a limit on how long a connection may be open.
6 >> If you have a low-bandwidth pipe, you'd be more vulnerable
7 >> to hitting that limit than someone with a high-bandwidth pipe.
8 >> Possible sources off the top of my head:
9 >> PHP scripts' script time limits, squid connection time limits.
10 >
11 > Yes, the limit is one of time, not of number of bytes transmitted.
12 > My earlier connection stayed open for 32 s & got 819 K ;
13 > one of the other repliers -- thanks to all -- got 38 s & the whole file.
14 >
15 > So 2 conclusions for me : (1) yes, servers do impose time-slices ;
16 > (2) my basic problem remains the very low bandwidth I'm getting,
17 > which I have to take up with my ISP once I've clarified other aspects.
18
19 There's probably nothing your ISP can do about it, unless you're
20 talking about upgrading your service.
21
22 One thing you might be able to do is pay $5/mo or so for a Linux VM at
23 some VPS provider, install and configure Squid, and bounce your own
24 traffic off of it. Squid will pull down the file faster than you, and
25 won't impose a connection time limit on you. (Unless you configure it
26 to do so...)
27
28 If you do something like that, be sure to properly secure it.
29
30 --
31 :wq

Replies

Subject Author
Re: [gentoo-user] I/net server throttling Adam Carter <adamcarter3@×××××.com>
Re: [gentoo-user] I/net server throttling Philip Webb <purslow@××××××××.net>