Ok, you guys' suggestions helped alot.
I changed --compress to --whole-file, and in fact that increased my speed from
4.5Mb/s to 18.5! Much better. Still core-bound though. (not disk, or network)
Now that I've finished my restore, I've run iperf.
Droog -- Hex 937 Mbits/sec!
Merlin -- Hex
I have a backup server now restoring 6TB of data to a client machine. This has
been going on for four days now, and no sign of getting close to completion.
The connexion is Gb enet end-to-end, and is running at only 40Mb/s. It has far
more capacity than that. The only limiting factor I can
On Tue, 2011-05-17 at 08:45 -0700, cac...@quantum-sci.com wrote:
The connexion is Gb enet end-to-end, and is running at only 40Mb/s.
It has far more capacity than that. The only limiting factor I can
see is on the backup server one core of the CPU is running 100% rsync.
Clearly rsync is not
Thanks, but the whole function of my backup server pivots on rsync features.
Need something rsync-like, but multi-threaded, or with a whole lot less
overhead.
On Tuesday 17 May, 2011 09:18:01 Chris Hawkins wrote:
I have no idea about potential rsync modifications, but you might try FDT to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Also, make sure you aren't running with compression as it will just
waste CPU cycles.
If you are running rsync over ssh it might also be worth while to setup
a one time use rsyncd or even NFS mount to eliminate the encryption
overhead.
On 05/17/11
at the server, it should be
in the hundreds of MB/s. If not rsync got stuck somewhere.
Multi-threading rsync is of little use because the the bottleneck will
be the disk IO.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https
On Tue, 17 May 2011, cac...@quantum-sci.com wrote:
In researching this I find that a change to multi-threaded goodness
would require a massive rewrite, and would only be considered for an
rsync replacement.
Abstracting the core functionality into a librsync.so would be really
spiffy too...
On Tuesday 17 May, 2011 10:43:21 you wrote:
Wow! That's a lot of data you're transferring into one server, even with a GB
pipe you're using, which appears to be using a fraction of it.
Yes, it's my home theater computer with all the movies. I've just set up a
RAID array and need to move my
On Tue, 2011-05-17 at 10:54 -0700, Chuck Wolber wrote:
On Tue, 17 May 2011, cac...@quantum-sci.com wrote:
In researching this I find that a change to multi-threaded goodness
would require a massive rewrite, and would only be considered for an
rsync replacement.
Abstracting the core
, and that Wayne has gotten as many bugs out of
it as he has over the last few years.
Agreed. I mostly meant that as tongue-in-cheek. Creating librsync.so seems
about as hard (or harder) as multi-threading.
..Ch:W..
--
An idea does not gain truth as it gains followers. Amanda Bloom
--
Please use
10 matches
Mail list logo
