From: Greg Freemyer <greg.freemyer@gmail.com>
To: cygwin@cygwin.com
Subject: Re: rsync performance degradation? Could be a windows issue?
Date: Mon, 11 Apr 2016 23:08:00 -0000 [thread overview]
Message-ID: <CAGpXXZKx19G-ixt5u59R+-5Rjn7yozwUEpLW1qFSY59Wckn8Yw@mail.gmail.com> (raw)
In-Reply-To: <CAGpXXZL9ZAJF_YSUOR=9WCvu+_K5Uub-zwWdpUV-yu7+OkYzFg@mail.gmail.com>
On Mon, Apr 11, 2016 at 2:20 PM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
> As I test, I just copied 30 GB of 1.5 GB files via robocopy. None of
> the files had been accessed since a reboot, so none should have been
> in cache.
>
> According to Resource Monitor, yes.
>
> I'm getting about 105 MB/sec for read and 105 MB/sec for write vs 70
> MB/sec for rsync.
I just moved both drives to a Linux box. Using the same rsync command
I'm getting 85 - 90 MB/sec.
That linux box is a 5-year old laptop, where as the windows box is a
pretty beefy box. (6 cores, 64 GB ram) Clearly the WIndows box
should be better performing and when running robocopy it is.
So it seems something about the combination of a Windows kernel,
cygwin, and rsync is dropping my performance at least a factor 20% and
maybe as much as 35%.
If I were to run rsync in strace, would anyone want to try and work on
the performance issue? Or should it just be chalked up to rsync being
optimized for a linux kernel?
Thanks
Greg
--
Greg Freemyer
www.IntelligentAvatar.net
--
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 prev parent reply other threads:[~2016-04-11 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 20:49 Greg Freemyer
2016-04-11 16:58 ` Greg Freemyer
2016-04-11 17:35 ` Marco Atzeri
2016-04-11 18:21 ` Greg Freemyer
2016-04-11 23:08 ` Greg Freemyer [this message]
2016-04-11 23:20 ` Vincent Rivière
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=CAGpXXZKx19G-ixt5u59R+-5Rjn7yozwUEpLW1qFSY59Wckn8Yw@mail.gmail.com \
--to=greg.freemyer@gmail.com \
--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).