From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Getting maximum space out of a hard drive
Date: Sat, 20 Aug 2022 16:57:51 -0400 [thread overview]
Message-ID: <CAGfcS_=VWKOtuhdEnHNJTfwafa2P6mG6iiT_AVKuTvFSG_b1yQ@mail.gmail.com> (raw)
In-Reply-To: <a30d83e3-5b6e-a6d9-2283-43819c4604f2@gmail.com>
On Sat, Aug 20, 2022 at 3:15 PM Dale <rdalek1967@gmail.com> wrote:
>
> Related question. Does encryption slow the read/write speeds of a drive
> down a fair amount? This new 10TB drive is maxing out at about
> 49.51MB/s or so.
Encryption won't impact the write speeds themselves of course, but it
could introduce a CPU bottleneck. If you don't have any cores pegged
at 100% though I'd say this isn't happening. On x86 encrypting a hard
drive shouldn't be a problem. I have seen it become a bottleneck on
something like a Pi4 if the encryption isn't directly supported in
hardware by the CPU.
50MB/s is reasonable if you have an IOPS-limited workload. It is of
course a bit low for something that is bandwidth-limited. If you want
to test that I'm not sure rsync is a great way to go. I'd pause that
(ctrl-z is fine), then verify that all disk IO goes to zero (might
take 30s to clear out the cache). Then I'd use "time dd bs=1M
count=20000 if=/dev/zero of=/path/to/drive/test" to measure how long
it takes to create a 20GB file. Oh, this assumes you're not using a
filesystem that can detect all-zeros and compress or make the file
sparse. If you get crazy-fast results then I'd do a test like copying
a single large file with cp and timing that.
Make sure your disk has no IO before testing. If you have two
processes accessing at once then you're going to get a huge drop in
performance on a spinning disk. That includes one writing process and
one reading one, unless the reads all hit the cache.
--
Rich
next prev parent reply other threads:[~2022-08-20 20:58 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 18:04 [gentoo-user] Getting maximum space out of a hard drive Dale
2022-08-18 18:18 ` Rich Freeman
2022-08-19 2:03 ` Dale
2022-08-19 4:26 ` David Haller
2022-08-24 22:45 ` Frank Steinmetzger
2022-08-25 6:22 ` William Kenworthy
2022-08-25 12:43 ` Dale
2022-08-25 12:52 ` Rich Freeman
2022-08-25 15:10 ` Jack
2022-08-25 18:59 ` Dale
2022-08-25 21:08 ` Rich Freeman
2022-08-25 23:59 ` Dale
2022-08-26 0:15 ` Mark Knecht
2022-08-26 11:26 ` Dale
2022-08-26 11:55 ` Gerrit Kuehn
2022-08-26 12:07 ` Rich Freeman
2022-08-26 23:07 ` Dale
2022-08-26 14:09 ` Mark Knecht
2022-08-26 14:25 ` Rich Freeman
2022-08-26 14:40 ` Mark Knecht
2022-08-26 23:20 ` Dale
2022-08-26 23:37 ` Mark Knecht
2022-08-27 1:16 ` Mark Knecht
2022-08-27 23:30 ` Dale
2022-08-28 9:27 ` Michael
2022-08-28 21:07 ` Frank Steinmetzger
2022-08-28 21:33 ` Wol
2022-08-28 21:53 ` Mark Knecht
2022-08-28 23:31 ` Wol
2022-08-28 21:34 ` Frank Steinmetzger
2022-08-29 5:49 ` Dale
2022-08-29 14:42 ` Frank Steinmetzger
2022-08-29 21:28 ` Dale
2022-08-30 14:26 ` Frank Steinmetzger
2022-08-25 22:41 ` Wols Lists
2022-08-25 23:56 ` Dale
2022-08-26 7:24 ` Wols Lists
2022-08-26 11:27 ` Dale
2022-08-26 13:35 ` Wols Lists
2022-08-26 4:47 ` David Haller
2022-08-18 18:20 ` Andreas Fink
2022-08-20 19:15 ` Dale
2022-08-20 20:57 ` Rich Freeman [this message]
2022-08-25 3:44 ` Dale
2022-08-20 21:46 ` Grant Taylor
2022-08-20 21:57 ` Grant Taylor
2022-08-20 22:45 ` Dale
2022-08-21 4:22 ` William Kenworthy
2022-08-21 5:34 ` Grant Taylor
2022-08-21 9:26 ` William Kenworthy
2022-08-21 10:09 ` Dale
2022-08-21 16:47 ` Dale
2022-08-21 5:27 ` Grant Taylor
2022-08-24 22:39 ` Frank Steinmetzger
2022-08-24 22:50 ` Wol
2022-08-22 14:50 ` Laurence Perkins
2022-08-22 15:02 ` Rich Freeman
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='CAGfcS_=VWKOtuhdEnHNJTfwafa2P6mG6iiT_AVKuTvFSG_b1yQ@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/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