INTL 3:770/1 3:770/3
REPLYADDR Pancho.Jones@proton.me
REPLYTO 3:770/3.0 UUCP
MSGID: fde7850f
REPLY: bea4a72f
PID: SoupGate-Win32 v1.05
On 21/02/2024 20:51, druck wrote:
> On 21/02/2024 17:42, Pancho wrote:
>> I got rid of my desire for an nvme with my opi5. Due to being PCIe 1
>> lane, it wasn't that much faster,
>
> That surprises me, could anyone with an NVMe base run this script which
> measures the maximum sequential and random access read/write speeds.
> You'll need to install the fio package and be in a directory on the disc
> under test.
>
I posted some stats back in December ( hdparm -Ttv), on the opi5 the
nvme was only giving 186 MB/s seq read, not that much more than a USB3
SSD at 137 MB/s.
I think, like the oPi5, the rPi5 also has the handicap that it only
allocates PCIe 3.0 x 1 to nvme.
So yes, nvme is faster in benchmarks, but nowhere near the 3000MB/s you
might see on a PC.
Perhaps more pertinently, the user experience improvement using the Pi
as an HTPC was negligible. I guess the performance I care about wasn't
constrained by disk read speed. So now I just run a SD card for the OS,
and pretty much everything else is NAS anyway.
I'm actually really happy with the rPi5 as a HTPC. I'm sitting in front
of the TV typing this.
> #!/bin/bash
> TESTFILE=fio-tempfile.dat
> fio --name SeqRead --eta-newline=5s --filename=$TESTFILE --rw=read\
> --size=500m --io_size=10g --blocksize=1024k --ioengine=libaio\
> --fsync=10000 --iodepth=32 --direct=1 --numjobs=1 --runtime=30\
> --group_reporting | grep bw=
> fio --name SeqWrite --eta-newline=5s --filename=$TESTFILE --rw=write\
> --size=500m --io_size=10g --blocksize=1024k --ioengine=libaio\
> --fsync=10000 --iodepth=32 --direct=1 --numjobs=1 --runtime=30\
> --group_reporting | grep bw=
> fio --name RndRead --eta-newline=5s --filename=$TESTFILE --rw=randread\
> --size=500m --io_size=10g --blocksize=4k --ioengine=libaio --fsync=1\
> --iodepth=1 --direct=1 --numjobs=1 --runtime=30 --group_reporting\
> | grep bw=
> fio --name RndWrite --eta-newline=5s --filename=$TESTFILE--rw=randwrite\
> --size=500m --io_size=10g --blocksize=4k --ioengine=libaio --fsync=1\
> --iodepth=1 --direct=1 --numjobs=1 --runtime=30 --group_reporting\
> | grep bw=
> rm $TESTFILE
>
>> and there was significant additional effort installing the OS,
>> compared to a micro SD. Obviously, you may have a different use-case.
>
> More than dd'ing the SD card image on to the NVMe, using gparted to
> expand the linux partition, and then changing the boot device in
> /boot/cmdline.txt and /etc/fstab ?
>
On the oPi5 there was DD (which I hate), and editing files on the boot
partition, on the onboard persistent ram. Not difficult, but still
enough to make mistakes. Whereas the Raspberry Pi Imager makes writing a
SD card really easy.
I've got at least one spare nvme sitting around, I'm not going to put it
on the rPi5.
My oPi5 is also booting off micro SD even though it has an nvme drive.
If Armbian ever rollout a stable version for the oPi5 I will stick it on
the nvme again, but I did it so many times I got pissed off.
In stark contrast, Pi OS has been solid on the rPi5.
> ---druck
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 128/260 129/305 135/225
SEEN-BY: 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1 6 226/17
SEEN-BY: 226/30 100 227/114 229/110 111 112 113 200 206 307 317 400
SEEN-BY: 229/426 428 470 550 616 664 700 240/1120 266/512 267/800
SEEN-BY: 282/1038 291/111 292/854 301/1 113 812 310/31 320/219 322/757
SEEN-BY: 335/364 341/66 342/200 396/45 460/58 633/280 712/848 770/1
SEEN-BY: 770/3 100 330 340 772/210 220 230 5020/400 1042 5058/104
SEEN-BY: 5075/35
PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426
|
