WANProxy in Subversion is working again.

[Uttam Singh]

Hi Juli,

Just wanted to share some early results from wanproxy svn r653:

- seeing great improvement in performance when moving data from Client
Proxy -> Server Proxy

Setup: 5Mbps symmetrical WAN, SMB file transfers (binary file ~11MB)

Without WanProxy:
Up: 4Mbps

With WanProxy:
Up: 14Mbps

- strange but did not observe any improvements over multiple transfers
of the same file in the other direction (Server Proxy -> Client Proxy)

- iperf tests are still failing. iperf send repeated text patterns
which should be great for deflation but I am seeing Client-Proxy
sending much more data to Server-Proxy than it receives from Client.

Client ------ Client-Proxy ................ Server Proxy ------ Server

Run:
Server> iperf -s -p 5100
Client> iperf -c -t 10 -p 5100 (10 sec test)

I see that client completes sending data to Client-Proxy followed by
TCP-FIN. Client-Proxy however continues sending data to Server-Proxy
for another ~30sec before closing. I haven't done any detailed
analysis except verify that iperf works successfully in the same setup
if I don't use WanProxy.

thanks,

-Uttam

On Tue, Dec 21, 2010 at 2:48 AM, Mallett, Juli <juli at clockworksquid.com> wrote:
> Hey folks,
>
> I've recently spoken with a few people who needed to try features that
> were only available in WANProxy in Subversion, but there were bugs
> that prevented testing.  I've been buried with work for the last six
> months, but have taken a few weeks off now, in which I'm working on a
> couple of exciting enhancements to WANProxy as well as catching up on
> bug fixes.
>
> As of right now (well, as of r650), I believe that I have fixed the
> bulk of the problems that people were seeing.  There may be a few edge
> cases, particularly related to connection teardown, but things look a
> lot better.  If I get positive feedback from other testers, I will
> probably put together a release before the end of the year, as well as
> one shortly into the new year.
>
> Please report any problems you see except for a crash when exiting due
> to ^C / SIGINT.  I have been working on infrastructure related to
> multithreading and have broken signal handling as a result, but that
> will be fixed in the near future.
>
> Thanks,
> Juli.
> _______________________________________________
> wanproxy mailing list
> wanproxy at lists.wanproxy.org
> http://lists.wanproxy.org/listinfo.cgi/wanproxy-wanproxy.org
>