From: "Michael Lemke" <lemkemch@t-online.de>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Local rsync disk to disk slow
Date: Sun, 04 Nov 2018 12:59:00 -0000 [thread overview]
Message-ID: <op.zryg1kowaqc5s6@orion.localdomain> (raw)
I am copying a large directory tree from one internal disk to another USB 3 connected disk on the same computer with this rsync line:
rsync -ahPvzHA --delete /d/Images /q/
This copies files at a rate of 20MB/s. If I copy the same tree with Windows Explorer I get about 90MB/s.
Why is this? The chosen options don't seem to affect the result much.
I noticed three rsync processes one of which is CPU bound at a single core and therefore limiting the performance. This process reads the source files. The other two rsync processes don't consume a noticable amount of CPU time and one of them writes the destination files.
Are there any options to speed up the process? The reason I use rsync is to preserve hard links.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2018-11-04 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 12:59 Michael Lemke [this message]
2018-11-04 14:21 ` Michael Lemke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.zryg1kowaqc5s6@orion.localdomain \
--to=lemkemch@t-online.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).