> -Original Message-
> From: Adam Goryachev [mailto:mailingli...@websitemanagers.com.au]
> Sent: den 11 oktober 2014 13:21
> To: backuppc-users@lists.sourceforge.net
> Subject: Re: [BackupPC-users] Unable to read 4 bytes revisited
>
> Try this:
> $sshPath -q -x -l root -p 522 $host $rsyncP
Hi all,
I'm seeing network speeds at about 35-45 Mbps when using BackupPC and rsync
over ssh.
Running iperf below I notice the network should theoretically be capable of a
bit more than that. I understand that ssh adds quite a bit of bottleneck.
[root@titan ~]# iperf -c cyndane
---
What about testing the speed over the ssh tunnel? That may tell you whether ssh
is slowing down your transfers or that it's due to rsync. If it is ssh, you
could trade encryption strength for speed.
Best,
Koen
On October 16, 2014 2:25:53 PM CEST, Sorin Srbu
wrote:
>Hi all,
>
>I'm seeing
You may wish to prevent ssh from using compression when using a fast
link, the overhead probably isn't worth it and may give you a reasonable
boost in throughput.
Like Koen said, you'll want to benchmark the different scenarios.
Regards,
Colin
On 16/10/14 16:28, Koen Vermeer wrote:
What abo
On Thu, Oct 16, 2014 at 7:25 AM, Sorin Srbu wrote:
>
> I'm seeing network speeds at about 35-45 Mbps when using BackupPC and rsync
> over ssh.
>
That sounds pretty good. But unless you have a lot of new files
created daily, the bottleneck is usually disk speed, especially
merging a lot of small
