I’m expecting to free up an NVMe SSD soon, and my Pi 5 is currently
making do with an SD card, so I’ve been looking into options for putting the two together.
Has anyone used this case?
https://shop.pimoroni.com/products/argon-neo-5-m-2-nvme-pcie-case-for-raspberry-pi-5
Another easily discoverable option is:
https://shop.pimoroni.com/products/nvme-base
...but I think I’d need a new case and I’ve not yet managed to find one that’s likely to fit.
Are there any other good options out there?
I’m expecting to free up an NVMe SSD soon, and my Pi 5 is currently
making do with an SD card, so I’ve been looking into options for putting the two together.
Has anyone used this case?
https://shop.pimoroni.com/products/argon-neo-5-m-2-nvme-pcie-case-for-raspberry-pi-5
Another easily discoverable option is:
https://shop.pimoroni.com/products/nvme-base
...but I think I’d need a new case and I’ve not yet managed to find one that’s likely to fit.
Are there any other good options out there?
I got rid of my desire for an nvme with my opi5. Due to being PCIe 1
lane, it wasn't that much faster,
and there was significant additional
effort installing the OS, compared to a micro SD. Obviously, you may
have a different use-case.
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.
#!/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 ?
---druck
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
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.
Pancho wrote:
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.
I think Jeff Geerling saw 900MB/s ?
fio --name SeqRead --eta-newline=5s --filename=$TESTFILE --rw=read\
--size=500m
On 22/02/2024 00:17, Andy Burns wrote:
Pancho wrote:
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.
I think Jeff Geerling saw 900MB/s ?
Remember, I'm testing nvme on an Orange Pi 5 not a Raspberry Pi 5, but,
I feel quite inadequate. However, it is what I get.
Here are the results from druck's script:
READ: bw=200MiB/s (209MB/s), 200MiB/s-200MiB/s (209MB/s-209MB/s), io=6000MiB (6291MB), run=30060-30060msec
WRITE: bw=199MiB/s (209MB/s), 199MiB/s-199MiB/s (209MB/s-209MB/s), io=6000MiB (6291MB), run=30085-30085msec
READ: bw=36.0MiB/s (37.8MB/s), 36.0MiB/s-36.0MiB/s
(37.8MB/s-37.8MB/s), io=1081MiB (1133MB), run=30001-30001msec
READ: bw=48.1MiB/s (50.4MB/s), 48.1MiB/s-48.1MiB/s
(50.4MB/s-50.4MB/s), io=1443MiB (1513MB), run=30001-30001msec
Maybe my result is so bad because I'm only using a KingSpec nvme drive?
It's supposed to do 3500MB/s, but I've never tested it in anything that
could handle that.
I'm not going to use a top range drive on a Pi. The Orange Pi isn't
doing anything else, isn't busy.
I was curious, so I did a bit of digging, it appears my nvme drive is
running as PCIe gen 1. The oPi5 should be gen 3, The nvme drive should
be gen 3.
Pancho wrote:
I was curious, so I did a bit of digging, it appears my nvme drive is
running as PCIe gen 1. The oPi5 should be gen 3, The nvme drive should
be gen 3.
I don't have an rpi5, but they also default to gen1, a config.txt option
can force gen3
dtparam=pciex1_gen=3
does an opi5 have similar?
I looked, I tried, I failed!
I tried adding the following line to /boot/armbianEnv.txt
'''
dtoverlay=pcie-gen2
'''
I also tried editing the dtb overlay: /boot/dtb/rockchip/rk3588s-orangepi-5.dtb
which was already configured for gen 2
Seriously, the oPi5 looks like a brilliant device, it feels like a
brilliant device, but nothing quite works properly, my advice is to buy
the rPi5, every time.
Here's the output of your script tested on my Pi5 with NVMe SSD:
READ: bw=850MiB/s (891MB/s), 850MiB/s-850MiB/s (891MB/s-891MB/s), io=10.0GiB
(10.7GB), run=12046-12046msec
WRITE: bw=746MiB/s (782MB/s), 746MiB/s-746MiB/s (782MB/s-782MB/s), io=10.0GiB
(10.7GB), run=13727-13727msec
READ: bw=64.6MiB/s (67.7MB/s), 64.6MiB/s-64.6MiB/s (67.7MB/s-67.7MB/s), io=1937MiB (2031MB), run=30000-30000msec
READ: bw=223MiB/s (234MB/s), 223MiB/s-223MiB/s (234MB/s-234MB/s), io=6684MiB
(7008MB), run=30000-30000msec
On Wed, 21 Feb 2024 20:51:31 +0000
druck <news@druck.org.uk> wrote:
fio --name SeqRead --eta-newline=5s --filename=$TESTFILE --rw=read\
--size=500m
Shouldn't that file size be much larger to prevent it from being
cached ? I get ridiculous numbers trying that script on a PC.
On 22/02/2024 10:00, Pancho wrote:
Here are the results from druck's script:
READ: bw=200MiB/s (209MB/s), 200MiB/s-200MiB/s (209MB/s-209MB/s),
io=6000MiB (6291MB), run=30060-30060msec
WRITE: bw=199MiB/s (209MB/s), 199MiB/s-199MiB/s (209MB/s-209MB/s),
io=6000MiB (6291MB), run=30085-30085msec
READ: bw=36.0MiB/s (37.8MB/s), 36.0MiB/s-36.0MiB/s
(37.8MB/s-37.8MB/s), io=1081MiB (1133MB), run=30001-30001msec
READ: bw=48.1MiB/s (50.4MB/s), 48.1MiB/s-48.1MiB/s
(50.4MB/s-50.4MB/s), io=1443MiB (1513MB), run=30001-30001msec
Check the line breaks didn't get messed up, as the last line should be
WRITE.
---druck
That's my general feeling. I think Armbian are trying to increase their
level of support for various board, but they are just volunteers with no
help from vendors.
I’m expecting to free up an NVMe SSD soon, and my Pi 5 is currently
making do with an SD card, so I’ve been looking into options for
putting the two together.
Has anyone used this case?
https://shop.pimoroni.com/products/argon-neo-5-m-2-nvme-pcie-case-for-raspberry-pi-5
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 65:55:18 |
Calls: | 100 |
Files: | 4,664 |
Messages: | 217,241 |