From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Very slow i/o to external hard drive's HFS+
Date: Wed, 16 Sep 2020 17:38:01 +0200 [thread overview]
Message-ID: <7b1c7554-70ed-47bd-3725-32ebaaea1822@towo.net> (raw)
In-Reply-To: <78677a3e-7f0c-d9e0-8542-6ab44ae5fe75@cruzio.com>
Am 16.09.2020 um 17:16 schrieb Rob Stevens:
> Hello
>
> I have a removable hard drive sporting an HFS+ connected to a USB3 port.
> The drive is a Seagate Slim Line 2T.
> I am using a driver from Paragon Sofware to write/read from this drive.
> I am running Windows10 build 19041.508 (ie up to date)
>
> Writing to this file system using the unix cp command is incredibly slow:
>
> cp my_file /cygdrive/h/some_destination
> The same write, using copy paste in Windows Explorer is much faster.
>
> I have not precisely timed it, but it is way more than an order of magnitude
> faster (a 1G file took approx 10 mins: the graphical display shows just
> a few seconds).
>
> (In Windows Device Manager I have the policy for the drive set to be
> "Better Performance" and not "Quick Removal" -- apparently
> the latter can lead to dramatic degradation in performance).
>
> Can anyone suggest what might be the cause?
"Better Performance" means that the write cache is active, so that the
copy could be reported finished before it actually is. So your
measurement may be deceptive. I assume cp applies some final flush, so
its result would be real while the Windows copy isn't. Please try to
change that setting for a reliable measurement.
Thomas
prev parent reply other threads:[~2020-09-16 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 15:16 Rob Stevens
2020-09-16 15:38 ` Thomas Wolff [this message]
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=7b1c7554-70ed-47bd-3725-32ebaaea1822@towo.net \
--to=towo@towo.net \
--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).