Subject: | |
From: | |
Reply To: | |
Date: | Mon, 11 Apr 2011 07:08:03 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
The limitation is not my hardware. The servers are both Dell R900 with SAS
disk arrays. Also, from a Windows virtual machine, inside the same server,
I get around 400 MB speed using FTP transfer, windows to windows. There
must be a different way to do this from Linux.The files are sparse files,
and I need to keep them that way, that's why I use rsync.
On 4/10/11 11:35 PM, "Larry Brower" <[log in to unmask]> wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA512
>
>On 04/11/2011 05:59 AM, Federico Alves wrote:
>> I am using rsync to send almost 1 TB of sparse files across the LAN to
>> another identical Linux box. If I fire only 1 command, I get about 22 Mb
>> of speed, but if I fire 6 commands in parallel, from different SSH
>> connections, the speed is divided by 6: very, very slow.
>>
>> My command is
>> rsync -S --progress sparsefile jephe@server:newsparsefile
>>
>> The LAN is 1GB and both machines are Scientific Linux 6.0.
>> Is there any way to do this that does not have a bottleneck?
>> Federico
>
>
>
>This could be a limitation of your disks speed in the servers and not
>rsync itself
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.10 (GNU/Linux)
>Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
>iQIcBAEBCgAGBQJNonb8AAoJEPXCUD/44PWqUYsP/0nJQ6lkVRUpfmQLXl9jv2NM
>pq6KfsCBwK8dWlylOCBx3JPUTCsE4tpnJzYHUsr6WNGRE6g9FAb4T2VfgZ/7TD9C
>LFzYpKboFWpRzcZlXVRz4k2CtTBi7aa+4bJCSrf/pVZCSBmMzZ2ZucwumMONjaSa
>RqHgJ6fnMDAfHX+Oq0edM9AQH9TRevDAsOBDj3CyBqb+FqnG7ZGMkOz2pUlPPG2S
>TtC43/71+6W1mx9Y3vRDykN96tG+SFXsSxqw/z7Ii94w3PtfpDXEuHPjCB0ZKmUu
>8w44nMq/cZlpF2MfEVJn7dmjXigY7Bsni7PNY8X2CfdepnofWFYdxAU14rPLw21d
>Ki+3VNXx4qStPfCJc2XXG6GegGETU5k0MJWc6ZgJDi0EAdHV0RagvPh2HTQ7ZGNU
>6gibeTTCGj4eucNiGco+/97t4++ED+fmPFcNm3G1kpbGO5hSQGPoC9lD4EdLE1Lk
>Z3jTD6v5I8hKrj6Jp8cpqkSASwL8F+aj/I7zpCFoTgN1nw9Y+O90CVau+EWcQKBo
>Ny3/IVlbBVHgaObKJM/MgA5B5BCLHmGJApGCwuvJVRPZ1ijYCZwHV/9rRTAZshO4
>qIZREj1fZEL/KnJylW/uEx6dCSegEHqZGvMLQeiIGd0mWDXaMeLJVcvXUzRcwncB
>VLjF8DoLtZdBDvtr2HYW
>=tcDp
>-----END PGP SIGNATURE-----
>
|
|
|