Can your disk do this?
https://imgur.com/a/xPfCkMy

On 2022-01-31 9:32 a.m., Commander Kinsey wrote:
> Can your disk do this?
> https://imgur.com/a/xPfCkMy

..

yes

On 31/01/2022 18:39, % wrote:
> On 2022-01-31 9:32 a.m., Commander Kinsey wrote:
>> Can your disk do this?
>> https://imgur.com/a/xPfCkMy
>
> .
>
> yes

*HOW* did YOU check?

On 2022-01-31 11:45 a.m., David Brooks wrote:
> On 31/01/2022 18:39, % wrote:
>> On 2022-01-31 9:32 a.m., Commander Kinsey wrote:
>>> Can your disk do this?
>>> https://imgur.com/a/xPfCkMy
>>
>> .
>>
>> yes
>
>
> *HOW* did YOU check?

i used a speed checker

In article <op.1gvb87krmvhs6z@ryzen.lan>, Commander Kinsey
<CK1@nospam.com> wrote:

> Can your disk do this?
> https://imgur.com/a/xPfCkMy

1gbyte/s is slow.

On 2022-01-31 12:15 p.m., nospam wrote:
> In article <op.1gvb87krmvhs6z@ryzen.lan>, Commander Kinsey
> <CK1@nospam.com> wrote:
>
>> Can your disk do this?
>> https://imgur.com/a/xPfCkMy
>
> 1gbyte/s is slow.
>
yes it is

On 1/31/2022 1:45 PM, David Brooks wrote:
> On 31/01/2022 18:39, % wrote:
>> On 2022-01-31 9:32 a.m., Commander Kinsey wrote:
>>> Can your disk do this?
>>> https://imgur.com/a/xPfCkMy
>>
>> .
>>
>> yes
>
>
> *HOW* did YOU check?

You can check with HDTune free edition on Windows.

I've only posted the URL for this, 259 times so far. http://www.hdtune.com/files/hdtune_255.exe

[Picture] if the image frame is empty, right click and select "Reload"

https://i.postimg.cc/1tPHhMkt/bench.gif

Top image is HDTune read-only benchmark. You can tell
it's not a hard drive.

The three others are File Explorer copy-pasta tests.

For each test, the test disk received a different cluster size setting.
And counter-intuitively, the smallest cluster size was the fastest (yikes!).

If Ken has time, Kens PCIe4 goes faster than anything I've got.
He had some checking to do, to make sure it was set up correctly.

There is a PCIe5 storage device now, but it was just
for Gelsinger to show off with (made by Samsung).

Paul

On Mon, 31 Jan 2022 20:19:12 -0000, Peter Jason <pj@jostle.com> wrote:

> On Mon, 31 Jan 2022 16:32:57 -0000, "Commander Kinsey"
> <CK1@nospam.com> wrote:
>
>> Can your disk do this?
>> https://imgur.com/a/xPfCkMy
>
> I get this thru a USB3 extension cable when I back up with Macrium8.

Bloody hell, I didn't realise USB went that fast. I take it you have 3.1 gen 2?

But I got it with a rotary disk!

On Mon, 31 Jan 2022 18:39:10 -0000, % <pursent100@gmail.com> wrote:

> On 2022-01-31 9:32 a.m., Commander Kinsey wrote:
>> Can your disk do this?
>> https://imgur.com/a/xPfCkMy
>
> .
>
> yes

Insufficient details.

Commander Kinsey wrote:
> Can your disk do this?
> https://imgur.com/a/xPfCkMy

After the buffer unloaded within the first few seconds the data transfer
settled in at the normal 333 MB/Sec.

On Fri, 04 Feb 2022 04:41:26 -0000, Paul in Houston TX <Paul@houston.texas> wrote:

> Commander Kinsey wrote:
>> Can your disk do this?
>> https://imgur.com/a/xPfCkMy
>
> After the buffer unloaded within the first few seconds the data transfer
> settled in at the normal 333 MB/Sec.

I don't call 333MB/sec normal for a rotary drive.

On 2/4/2022 5:21 PM, Commander Kinsey wrote:
> On Fri, 04 Feb 2022 04:41:26 -0000, Paul in Houston TX <Paul@houston.texas> wrote:
>
>> Commander Kinsey wrote:
>>> Can your disk do this?
>>> https://imgur.com/a/xPfCkMy
>>
>> After the buffer unloaded within the first few seconds the data transfer
>> settled in at the normal 333 MB/Sec.
>
> I don't call 333MB/sec normal for a rotary drive.

There is one 15K hard drive, that does 300MB/sec.
That is the fastest read channel I've ever heard of
on a hard drive.

*******

Your OS has a System Read Cache and a System Write Cache.

Now you know where "wavy gravy" comes from. Too much
interference from the OS.

Linux is similar, in the "interference department".

One difference in Linux, is you can drop the cache
with a command, which invalidates the System Read Cache
saving lots of time for the experimenter. The write cache
should not drop, because the memory in it is committed,
and the status of that memory won't change until it is
drained of content.

sudo /sbin/sysctl -w vm.drop_caches=3

Paul

On 05/02/2022 00:12, Paul wrote:
> Now you know where "wavy gravy" comes from.

OT - Fun! :-)

https://www.facebook.com/annextechnologies

On Sat, 05 Feb 2022 00:12:16 -0000, Paul <nospam@needed.invalid> wrote:

> On 2/4/2022 5:21 PM, Commander Kinsey wrote:
>> On Fri, 04 Feb 2022 04:41:26 -0000, Paul in Houston TX <Paul@houston.texas> wrote:
>>
>>> Commander Kinsey wrote:
>>>> Can your disk do this?
>>>> https://imgur.com/a/xPfCkMy
>>>
>>> After the buffer unloaded within the first few seconds the data transfer
>>> settled in at the normal 333 MB/Sec.
>>
>> I don't call 333MB/sec normal for a rotary drive.
>
> There is one 15K hard drive, that does 300MB/sec.
> That is the fastest read channel I've ever heard of
> on a hard drive.
>
> *******
>
> Your OS has a System Read Cache and a System Write Cache.

It wasn't that, I forgot I'd compressed that disk. Those terribly fast files were partially downloaded torrents, mainly blank space.

> Now you know where "wavy gravy" comes from. Too much
> interference from the OS.
>
> Linux is similar, in the "interference department".
>
> One difference in Linux, is you can drop the cache
> with a command, which invalidates the System Read Cache
> saving lots of time for the experimenter. The write cache
> should not drop, because the memory in it is committed,
> and the status of that memory won't change until it is
> drained of content.
>
> sudo /sbin/sysctl -w vm.drop_caches=3
>
> Paul

On Sat, 05 Feb 2022 00:17:51 -0000, wrote:

> On 05/02/2022 00:12, Paul wrote:
>> Now you know where "wavy gravy" comes from.
>
> OT - Fun! :-)
>
> https://www.facebook.com/annextechnologies

Gay web design ROTFPMSL!

On 05/02/2022 20:05, Commander Kinsey wrote:
> On Sat, 05 Feb 2022 00:17:51 -0000,  wrote:
>
>> On 05/02/2022 00:12, Paul wrote:
>>> Now you know where "wavy gravy" comes from.
>>
>> OT - Fun! :-)
>>
>> https://www.facebook.com/annextechnologies
>
> Gay web design ROTFPMSL!

I hoped someone would look! :-D

The John Doe troll stated the following in message-id
<sdhn7c$pkp$4@dont-email.me>:

> The troll doesn't even know how to format a USENET post...

And the John Doe troll stated the following in message-id
<sg3kr7$qt5$1@dont-email.me>:

> The reason Bozo cannot figure out how to get Google to keep from
> breaking its lines in inappropriate places is because Bozo is
> CLUELESS...

NOBODY likes the John Doe troll's contentless spam.

And yet, the clueless John Doe troll has continued to post incorrectly
formatted USENET articles that are devoid of content (latest example on
Sun, 13 Feb 2022 06:50:34 -0000 (UTC) in message-id
<sua9np$uhm$6@dont-email.me>).

This posting is a public service announcement for any google groups
readers who happen by to point out that the John Doe troll does not even
follow the rules it uses to troll other posters.

E/OMCHglTpmn

On Sun, 13 Feb 2022 06:50:34 -0000, John Doe <always.look@message.header> wrote:

> Mine are much faster.
>
> https://www.flickr.com/photos/27532210@N04/?
>
> Silly troll...

How is a picture under a tennis player's legs anything to do with disk speed?

And post at the bottom you newbie.

The John Doe troll stated the following in message-id
<sdhn7c$pkp$4@dont-email.me>:

> The troll doesn't even know how to format a USENET post...

And the John Doe troll stated the following in message-id
<sg3kr7$qt5$1@dont-email.me>:

> The reason Bozo cannot figure out how to get Google to keep from
> breaking its lines in inappropriate places is because Bozo is
> CLUELESS...

NOBODY likes the John Doe troll's contentless spam.

And yet, the clueless John Doe troll has continued to post incorrectly
formatted USENET articles that are devoid of content (latest example on
Mon, 14 Feb 2022 07:54:22 -0000 (UTC) in message-id
<sud1re$uv6$2@dont-email.me>).

This posting is a public service announcement for any google groups
readers who happen by to point out that the John Doe troll does not even
follow the rules it uses to troll other posters.

+t++oh9iBNiT

The John Doe troll stated the following in message-id
<sdhn7c$pkp$4@dont-email.me>:

> The troll doesn't even know how to format a USENET post...

And the John Doe troll stated the following in message-id
<sg3kr7$qt5$1@dont-email.me>:

> The reason Bozo cannot figure out how to get Google to keep from
> breaking its lines in inappropriate places is because Bozo is
> CLUELESS...

And yet, the clueless John Doe troll has itself posted yet another
incorrectly formatted USENET posting on Mon, 14 Feb 2022 08:00:49 -0000
(UTC) in message-id <sud27h$uv6$3@dont-email.me>.

This posting is a public service announcement for any google groups
readers who happen by to point out that the John Doe troll does not even
follow it's own rules that it uses to troll other posters.

AENRfBtL38pP

On Mon, 14 Feb 2022 07:54:22 -0000, John Doe <always.look@message.header> wrote:

> Silly troll...

Did you forget to quote?