Re: [squid-users] Re: squid with pdns, bandwidth control issue

From: Muhammad Yousuf Khan <sirtcp_at_gmail.com>
Date: Mon, 2 Jul 2012 12:48:41 +0500

On Fri, Jun 29, 2012 at 9:41 PM, Ed W <lists_at_wildgooses.com> wrote:
> On 29/06/2012 14:12, Muhammad Yousuf Khan wrote:
>>
>> i have made some test and here is some detail and results
>> ok i am using two machine
>>
>> 1, Gateway IPcop (linux)
>> 2. Debian lenny (squid)
>>
>> i am using download manager to download a 50MB file.
>>
>> IPCOP
>> -----------
>> when i do it VIA IPCOP my download burst rate up to 270 KB
>> not ping delay and other can also brows easily.
>>
>> Squid on Lenny
>> ------------------------
>>
>> VIA SQuid (proxy mode) my download reach 365 which is full throughput
>> and faster then IPCOP but
>> ping delay reach 4000 which is considered almost near to death.
>>
>> and no other users can brown and getting time out message on there
>> browser.
>>
>>
>> i think this shows that issue is with squid box and i don't know
>> weather i have to tweak the squid or TCP buffer or anything
>>
>
> Run a download using wget from both boxes and observe the download speeds
> and effect on ping. This might help you figure out if it's an operating
> system configuration setting

i think we don't have to run the test let see the internal diagram of
my network

                   ========Proxy Server========
                  || ||
<IPcop Linux firewall> <LAN>
                  || ||
                   =======MS ISA server========

i hope that above diagram would be easy to understand however let me
explain a bit.

1. IPcop is a core layer firewall directly connected to Fiber/Ethernet
 provided by the ISP
2. IPcop LAN wire is connected to a switch. and with a switch i am
using two flavors of proxy. 1 is MS ISA 2006 and second one is Squid.
3. my squid box is a proxy only but setup as firewall. for example.
one Ethernet interface is for out side and one for LAN.
4. Finally the third layer is my LAN network. and according to this
diagram my ISA is working fine. however squid is more flexible and
comprehensive then MS ISA but in bandwidth control it is not working
like ISA. (may be my mistake)

when ever i downloaded some thing VIA ISA it gives me accurate result.
for example, when i browse some thing, it actually trims down the
bandwidth of downloading and gave priority to browsing. and give other
users a change to do browsing and downloading and controlling
bandwidth according to the availability and user queries.

now in squid when download starts it actually stops everything except
the single download session.

This result is direct squid box download.
----------------------------------------------------------
 it reaches 350K which is a max and fortunately when i download some
thing or brows some thing from client computer things work fine.(
bandwidth of the download trims down and priority given to the
browsing traffic). but when i download some thing from client computer
it stuck to the max download and rest of the users can not even brows.

wget Resolving garr.dl.sourceforge.net... 193.206.140.34, 2001:760:ffff:b0::34
Connecting to garr.dl.sourceforge.net|193.206.140.34|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 383395840 (366M) [application/octet-stream]
Saving to: ‚systemrescuecd-x86-2.6.0.iso‚

10% [=======>
             ] 40,047,336 313K/s eta 17m 50s ^C
root_at_proxy-prod-mirror:~#
http://garr.dl.sourceforge.net/project/systemrescuecd/sysresccd-x86/2.6.0/systemrescuecd-x86-2.6.0.iso

NOTE : the reason of using two proxy because i am about to shift my
network from ISA to Squid. in short i want to get rid of ISA.

 effect is clear though - one of your machines is managing to max out the
> entire inbound connection (which is exactly what TCP is supposed to try and
> do). The other machine is only partially using the connection (I know that
> feels more desirable, but it's likely an accident and it's not how tcp tries
> to behave)
>
> So your problem seems to be reduced to figuring out why one machine is
> performing optimally and hence hogging the whole internet connection.
>
> Reduce the problem to the basics and debug from there. Just remember that
> tcp is supposed to learn how to hog the entire connection, allocating
> traffic more evenly is a tricky problem and you might want to use the
> various features in squid delay pools and linux traffic control to control
> this..?
>
> Good luck
>
> Ed W
Received on Mon Jul 02 2012 - 07:48:48 MDT

This archive was generated by hypermail 2.2.0 : Mon Jul 02 2012 - 12:00:02 MDT