public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: Mario Emmenlauer <mario@emmenlauer.de>,
	Adam Kessel <adam@rosi-kessel.org>,
	cygwin@cygwin.com
Subject: Re: Faster rsync?
Date: Tue, 29 Aug 2023 09:43:30 -0400	[thread overview]
Message-ID: <b99a98ee-bc82-e930-b8ea-56776af062d0@cs.umass.edu> (raw)
In-Reply-To: <4a3ca0f6-128e-adb7-0140-cacb20f06544@emmenlauer.de>

On 8/29/2023 9:17 AM, Mario Emmenlauer via Cygwin wrote:
> On 29.08.23 14:32, Adam Kessel via Cygwin wrote:
>> I've found rsync to be painfully slow on large folders -- hours to sync thousands of files, even 
>> when they already match size and --size-only is used. It's much faster between native Linux boxes.

I've been told (on this list) that how you mount the Windows drive in Cygwin matters.

I use this in my /etc/fstab:

d:/ /cygdrive/d ntfs binary,posix=0,user,auto,notexec 0 0

Unfortunately, it's still not as quick as I think it ought to be.
(If someone out there can recommend better settings, I'm open!)

I regularly rsync a collection of hundreds of files, each about 2Gb in size.

Windows describes the partition as an NTFS Basic Data Partition.  It takes
rsync a long time to get started (i.e., to figure out which files need
transferring).

My rsync uses these flags:

rsync -avuP --partial --partial-dir=.rsync-partial --log-file=... --log-file-format=...

> I've been using rsync, unison and similar tools on Windows and Linux since basically forever. In my 
> humble opinion, the problem is the Windows file system performance, not the synchronization tools. 
> As a separate example, try to download the boost source code, and extract the archive. I can do the 
> extraction in way under a minute on Linux, but have to wait many many minutes on a similarly 
> equipped Windows machine.
> 
> Just my two cents.
> 
>      Mario
> 

Regards - Eliot Moss

  reply	other threads:[~2023-08-29 13:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29 12:32 Adam Kessel
2023-08-29 13:17 ` Mario Emmenlauer
2023-08-29 13:43   ` Eliot Moss [this message]
2023-08-29 17:55     ` Eliot Moss

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=b99a98ee-bc82-e930-b8ea-56776af062d0@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=adam@rosi-kessel.org \
    --cc=cygwin@cygwin.com \
    --cc=mario@emmenlauer.de \
    /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).