From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New hard drive. Is this normal? It looks like a connect problem.
Date: Tue, 13 May 2025 09:30:50 +0100 [thread overview]
Message-ID: <2369736.ElGaqSPkdT@rogueboard> (raw)
In-Reply-To: <aCJ3fNhQ7hPdpruQ@schatulle>
[-- Attachment #1: Type: text/plain, Size: 1858 bytes --]
On Monday, 12 May 2025 23:34:36 British Summer Time Frank Steinmetzger wrote:
> Am Wed, May 07, 2025 at 09:18:16AM +0100 schrieb Michael:
> > On Wednesday, 7 May 2025 00:30:34 British Summer Time Dale wrote:
> > > […]
> > > I ran a hdparm test. I wanted to see as accurately as I could what the
> > > speed was. I got this.
> > >
> > >
> > >
> > > root@nas ~ # hdparm -tT /dev/sdb
> > >
> > > /dev/sdb:
> > > Timing cached reads: 7106 MB in 2.00 seconds = 3554.48 MB/sec
> >
> > These are rather pedestrian ^^^^ but I do not have any drives as large as
> > yours to compare. A 4G drive here shows this:
> >
> > ~ # hdparm -tT /dev/sda
> >
> > /dev/sda:
> > Timing cached reads: 52818 MB in 1.99 seconds = 26531.72 MB/sec
> > Timing buffered disk reads: 752 MB in 3.00 seconds = 250.45 MB/sec
> >
> > That's an order of magnitude higher cached reads.
>
> So you have a faster machine, possibly DDR5.
Not sure if its faster, but it only has DDR4.
> Dale’s NAS is an old build.
I didn't know with certainty what PC it was connected to at the time.
> That’s why it’s called cached.
>
> From the manpage of hdparm: This measurement [of -T] is essentially an
> indication of the throughput of the processor, cache, and memory of the
> system under test. This displays the speed of reading directly from the
> Linux buffer cache without disk access.
> -------------------^^^^^^^^^^^^^^^^^^^
You are right of course, thank you for point this out. I was wondering if the
cached speeds may have been affected by the drive spinning down, but not
spinning up fast enough when the test starts and this affecting the reading,
or a bad cable. The difference in speed looked too high to me and I was
looking for anything pointing to a bad connection between the drive and the
PC.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-05-13 8:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 21:15 [gentoo-user] New hard drive. Is this normal? It looks like a connect problem Dale
2025-05-06 12:12 ` Michael
2025-05-06 12:59 ` Dale
2025-05-06 14:31 ` Michael
2025-05-06 20:51 ` Dale
2025-05-06 23:08 ` Wol
2025-05-07 0:16 ` Dale
2025-05-06 23:30 ` Dale
2025-05-07 8:18 ` Michael
2025-05-07 15:13 ` Dale
2025-05-10 15:53 ` Dale
2025-05-10 18:52 ` Michael
2025-05-12 8:11 ` Dale
2025-05-12 11:14 ` Michael
2025-05-13 6:30 ` Dale
2025-05-12 22:34 ` Frank Steinmetzger
2025-05-13 6:05 ` Dale
2025-05-13 8:30 ` Michael [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=2369736.ElGaqSPkdT@rogueboard \
--to=confabulate@kintzios.com \
--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