From owner-freebsd-net@FreeBSD.ORG Wed Nov 21 17:32:06 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 655DF5F0 for ; Wed, 21 Nov 2012 17:32:06 +0000 (UTC) (envelope-from marc@mpeters.org) Received: from mail.mpeters.org (mail.mpeters.org [78.46.104.142]) by mx1.freebsd.org (Postfix) with ESMTP id F39648FC12 for ; Wed, 21 Nov 2012 17:32:05 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.mpeters.org (Postfix) with ESMTP id D1AC213200F; Wed, 21 Nov 2012 18:32:04 +0100 (CET) X-Virus-Scanned: amavisd-new at mpeters.org Received: from mail.mpeters.org ([127.0.0.1]) by localhost (mail.mpeters.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jtrZpvUxrXoI; Wed, 21 Nov 2012 18:32:02 +0100 (CET) Received: from [192.168.0.204] (unknown [62.159.86.18]) by mail.mpeters.org (Postfix) with ESMTPSA id A648B13200E; Wed, 21 Nov 2012 18:32:02 +0100 (CET) Message-ID: <50AD1012.7020209@mpeters.org> Date: Wed, 21 Nov 2012 18:32:02 +0100 From: Marc Peters User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121104 Thunderbird/16.0.1 MIME-Version: 1.0 To: Benjamin Villain Subject: Re: Low Bandwidth on intercontinental connections References: <50ACF62C.8000408@mpeters.org> <50ad087d.1892cc0a.2cce.3bf2@mx.google.com> In-Reply-To: <50ad087d.1892cc0a.2cce.3bf2@mx.google.com> X-Enigmail-Version: 1.5a1pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2012 17:32:06 -0000 On 11/21/2012 05:58 PM, Benjamin Villain wrote: > I don't think this is about disk or memory leak as transfering files > locally seem to work fine. > > Can you test transferring files from (and to) your Linux boxes to (and > from) the FreeBSD servers to check that it is not a network issue inside > your DCs. > > King regards, > > -- > Ben Hi Ben, i don't think this is memory related, too. We used plain CLI scp ot ftp from base, both times. Here is the requested data: Linux ---> FreeBSD: root@linux:~# scp jdk-6u33-linux-x64.bin 172.16.3.10: Password: jdk-6u33-linux-x64.bin 89% 61MB 59.0KB/s FreeBSD ---> Linux: [root@freebsd ~]# scp test.tgz 172.16.4.50: Password: test.tgz 100% 59MB 1.1MB/s 00:55 [root@freebsd ~]# >From BSD to Linux is not as fast as L <--> L. I don't think, this is network related in some sort. Marc > > Mehmet Erol Sanliturk writes: > >> On Wed, Nov 21, 2012 at 7:41 AM, Marc Peters wrote: >> >> > Hi list, >> > >> > we are experiencing low throughput on interncontinental connections >> with >> > our FreeBSD Servers. We made several tests and are wondering, why this >> > would be. The first tests were on an IPSEC VPN between our >> datacenter in >> > DE and Santa Clara, CA. We are connected with two gigabit uplinks in >> > each DC. Pushing data by scp between our FreeBSD servers takes ages. >> > Starting with several MB/s it drops to 60-70KB/s: >> > >> >> >> >> ..... >> >> >> I do not have any answer to your question , but I want to share one my >> experiences . >> >> I Linux ( KDE ) I was copying a hard disk contents to another drive by >> using Dolphin . >> At the beginning it was very fast , but over time its speed reduced to a >> few kilobytes per second . >> It listed completion time left as months . >> >> I inspected why this is the case . >> >> The reason was the following : >> >> On each file it is copied , the Dolphin was producing approximately 1 >> Kilobyte memory leak . >> After copying more than one million file , all of the memory exhausted >> and >> it started to swap >> memory to hard disk swap space which reduced copy speed to a few >> kilobytes >> per second . >> >> >> I stopped the Dolphin and copied small directory groups by restarting the >> Dolphin . This cured the problem because on each exit , all of the leaked >> memory by Dolphin has been disposed ( where "Undo" item of Dolphin >> menu was >> disabled means memory is not reserved for undo ). >> >> >> Please study your data transfer software for such a possibility . It may >> not be problematic in Linux but FreeBSD version may have some trouble >> points . >> >> >> There is another possibility : Graceful degradation . >> >> http://en.wikipedia.org/wiki/Graceful_degradation >> http://en.wikipedia.org/wiki/Fail_soft >> >> A program part may produce graceful degradation over time or processed >> data >> : >> >> For example , assume a list is searched by sequentially . When list >> length >> grows , search times >> also grows linearly and produces a degradation although there is no any >> error in the process . >> >> You may study your system with respect to such a process . >> >> >> These are the possibilities which come to my mind . >> >> >> Thank you very much . >> >> Mehmet Erol Sanliturk >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"