huge difference using wanproxy throught internet

[Juli Mallett]

Hi Daniel,

With a lower-latency link like a WAN rather than the Internet, I would
expect to see more packets sent between WANProxy instances; WANProxy makes
no effort to buffer up data before sending it.  Using a slower link, you'll
naturally have more buffering occurring and fewer packets sent.  There's
some things that we could do and should do to avoid sending out gratuitous
small packets, and I have some changes to do that, but I haven't tested
them enough to check them in yet.

I'm not sure if I understand the difference you're seeing in terms of data
reduction / deduplication / compression.  Which is giving the greater
savings in terms of data transferred, the LAN or the Internet?  And what
kind of download time are you seeing to the client on each configuration?

Thanks,
Juli.


On Fri, Aug 16, 2013 at 8:25 AM, Daniel Coletti <dcoletti at xtech.com.ar>wrote:

> Hi,
>     We're testing wanproxy heavily and during the tests we saw a baffling
> traffic saving difference between using wanproxy inside a LAN and using it
> trought the internet.
>
> Under Linux (ubuntu 12.04 client side and debian 7.0 on the server).
> The first set up is like this (we used an iso file for testing):
> WPclient->(gateway)->//internet//->WPserver+squid->//internet//->webserver
>
> 1st. download:
> traffic between wanproxies = 218.000 tcp packs, 183 mbytes
> traffic between wanproxy client and PC inside the LAN = 29.412 tcp packs,
> 177Mb
>
>  2nd download:
> about 10% traffic saving equally disperse between tcp packs and mbytes
> sent between wanproxies
>
> the second set up is like this (the same iso file):
> WPcliente->(LAN)WPserver+squid->(LAN)->webserver
> 1st. download:
> traffic between wanproxies = 104.000 tcp packs, 143 mbytes
> traffic between wanproxy client and PC inside the LAN = 7844 tcp packs,
> 177Mb
>
> 2nd download:
> traffic between wanproxies = 8230 tcp packs, *10* mbytes
> traffic between wanproxy client and PC inside the LAN = 4090 tcp packs,
> 176Mb
>
> The first thing I notice was the huge difference in the tcp packs sent
> during the first download of both setups (Internet vs. LAN) 218K vs 104K,
> but the differences between the first and second download using LAN is 20%
> saving using internet, 95% saving using LAN.
>
> Following Diego Woitasen's advice I tried manipuling the MTU with MSS
> Clamping (http://lartc.org/howto/lartc.cookbook.mtu-mss.html) and it got
> better (up to 30% savings).
>
> Using internet the number of tcp packets sent between wanproxies grew from
> 104K  (in LAN) to 218K (more than 100%).
>
> Any ideas on how to go around this problem? Is there something that can be
> done inside wanproxy's code?
>
> thanks,
>
> dc//
>
> --
> Daniel Coletti
> Director
> XTech (Soluciones Linux para Empresas) - http://www.xtech.com.ar
> ++(5411) 5219-0678
> 25 de Mayo 460 - 3er. piso
> Buenos Aires, Argentina
>
> _______________________________________________
> wanproxy mailing list
> wanproxy at lists.wanproxy.org
> http://lists.wanproxy.org/listinfo.cgi/wanproxy-wanproxy.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wanproxy.org/pipermail/wanproxy-wanproxy.org/attachments/20130816/13c622c6/attachment-0003.htm>