Re: [squid-users] 3.1.0.14 tproxy slow preformance

Amos Jeffries wrote:
> Dan wrote:
>> Hello,
>>
>> I have compile squid 3.1.0.14 under both Ubuntu 9.04 and Fedora 11.
>> Both complete successfully and work fine until I enable tproxy then
>> the requests performance drops.
>>
>> here is a httperf of squid without tproxy
>>
>> httperf --client=0/1 --server=localhost --port=3128 --uri=/
>> --send-buffer=4096 --recv-buffer=16384 --num-conns=1 --num-calls=1
>> Maximum connect burst length: 0
>>
>> Total: connections 1 requests 1 replies 1 test-duration 0.003 s
>>
>> Connection rate: 316.1 conn/s (3.2 ms/conn, <=1 concurrent connections)
>> Connection time [ms]: min 3.2 avg 3.2 max 3.2 median 3.5 stddev 0.0
>> Connection time [ms]: connect 0.9
>> Connection length [replies/conn]: 1.000
>>
>> Request rate: 316.1 req/s (3.2 ms/req)
>> Request size [B]: 62.0
>>
>> here is a httperf of squid with tproxy
>>
>> httperf --client=0/1 --server=localhost --port=3128 --uri=/
>> --send-buffer=4096 --recv-buffer=16384 --num-conns=1 --num-calls=1
>> Maximum connect burst length: 0
>>
>> Total: connections 1 requests 1 replies 1 test-duration 0.103 s
>>
>> Connection rate: 9.7 conn/s (102.7 ms/conn, <=1 concurrent connections)
>> Connection time [ms]: min 102.7 avg 102.7 max 102.7 median 102.5
>> stddev 0.0
>> Connection time [ms]: connect 0.6
>> Connection length [replies/conn]: 1.000
>>
>> Request rate: 9.7 req/s (102.7 ms/req)
>> Request size [B]: 62.0
>>
>> Any help would be greatly appreciated.
>>
>> Dan
>
> By the looks of those test lines you seem to be sending regular
> forward-proxy requests to port 3128 with tproxy flagged on that port?
>
> That will cause worst-case processing in the kernel, error signals and
> process, additional logging actions, and at least two connection
> attempts to be made with Async time delays between each step.
>
> You need to test with #2 going direct to the fake server port 80 and
> the iptables rules catching the TCP link in order to get a real
> capacity measure of TPROXY.
>
> Amos
Thank you for the fast reply and explaining my testing error to me.
Once I enable the tproxy rule all speeds are normal.

Dan
Received on Sun Oct 04 2009 - 22:59:42 MDT