Storage options continue to advance at a very fast pace. We’ve seen a lot of changes in the past couple of years with viable storage options for your Pi. Solid state drives are now so cheap that it can be cheaper to outfit your Pi with a SSD than buy a MicroSD card! MicroSD cards also continue to evolve with the new “Application Class” A1 and A2 certifications.
This year I wanted to do something more than just benchmark my ever-growing pile of MicroSD cards and solid state drives. Although I have a wide variety of storage to test I don’t have everything! So this time I created a benchmark that gives you a easy to compare score and anonymously submits the storage specifications and the results to this site.
Running the benchmark is extremely easy. Run the following command on your Pi:
sudo curl https://raw.githubusercontent.com/TheRemote/PiBenchmarks/master/Storage.sh | sudo bash
Current Benchmark Results
Pi Benchmarks – Raspberry Pi Storage Benchmarks
The 2022 storage benchmarks are now available!
Navigating the Results
As the list of submissions continues to grow there can be a lot of data to sift through. I’ve provided a filter on the table to help narrow some of that down.
To only see Micro SD cards click the “Product” drop down from the options above the table and choose “SD”. This will filter out everything but Micro SD cards. To see solid state choose “SSD”. You can also search by manufacturer, brand, etc.
I have also offered the option to export the entire results table to Excel and other formats. If you perform any advanced analysis that you think would be useful to share be sure to leave a comment with what you found and I will credit you and post it for everyone!
Scoring
The benchmark heavily favors 4k random reads / writes. This is because for application and operating system performance this is by far the most important metric. Traditional benchmarking methods like dd write, hdparm read tests, etc. are very poor indicators of everyday performance. What matters is not how fast your storage can push through giant files but how fast it can respond to random input that asks it to read / write anywhere on the disk.
To understand why we need to think of what your Raspberry Pi is usually doing. Most applications and services are not constantly writing giant sequential files which is what traditional synthetic benchmarks measure. Your Raspberry Pi is usually updating log files, reading data from different parts of the disk for various applications and services, responding to user input, etc. To your disk drive this behavior is considered “random” since it has no idea what it will be asked to read / write next.
Storage devices doing large sequential I/O like transferring files utilize extensive caching and other techniques to speed up these kinds of operations. Unfortunately these techniques do not work when the operating system and storage device doesn’t know what users / applications / services might request next. The storage device has no way to know or prepare for what your application will want next so it has to read it raw from the disk and can’t rely on cache.
This is why in our benchmarking we want to look very hard at 4k random read / writes. This is what will determine how “snappy” the Pi feels as you perform various tasks. Fast 4k random IO devices feel and perform much better than a device with huge throughput but poor random I/O performance.
The current scoring method is:
(DDWriteSpeed * 1024 + fio4kRandReadIOPS * 4 + fio4kRandWriteIOPS * 10 + io4kRead + io4kWrite + IO4kRandRead * 4 + IO4kRandWrite * 10) / 100
Methodology
The benchmark runs a few different tests in order to get a good overall idea of storage performance. It runs 4k read / write and random read / write in two separate benchmarks to verify the results and reduce variance. Here are the tests used in the benchmark:
FIO – An industry standard used for true storage benchmarking vs. just measuring throughput (like DD Write and HDParm — not considered true benchmarks). The benchmark tests 4k block size sequential read/write and random read/write. Gives a result in IOPS which stands for Input/Output Operations Per Second
IOZone – A very popular benchmarking program. We also test 4k block size sequential read / write and 4k random read / writes here to verify our results are close to the FIO results
DD Write – Basic throughput test of writing 0’s as fast as possible
HD Parm – Tests disk read throughput in direct mode (avoids caching)
Recommendations
The top recommendation this year for Pi storage will depend on your form factor. Let’s break it down:
My project is stationary (servers, media centers, etc.)
The best choice is a 2.5″ Solid State drive connected via USB. This is the highest performance choice and is very cheap.
If you have a Pi 3B+ or older the benchmarks show that any solid state drive is so fast that it maxes out the Raspberry Pi’s USB 2.0 bus. I’ll talk about this more in the SSD analysis section below but basically it’s best to get the cheapest option while still picking a reliable brand.
If you have a Pi 4 then the performance of the solid state that you get is a performance factor. Differences between drive quality can affect performance but the performance of *any* quality solid state drive is going to crush SD cards and USB flash drives.
The best way to find good fast drives is to go to the full Pi Storage Benchmark results and soft by drive and see which ones score higher and by how much. When you look at prices you can determine if you want to pay extra for the highest classes of performance and where your sweet spot is.
The new Pi 4 has a much faster USB 3.0 bus on it that allows solid state’s potential to be unleashed leading to huge performance gains.
Here is my current recommendation:
The Kingston A400 has been a great drive to use with the Pi for years. It’s reliable, widely available around the world, has low power requirements and performs very well. It’s also very affordable. This drive has been benchmarked over 1000 times at pibenchmarks.com and is the #1 most popular SSD among the Pi community!
Links: AliExpress*, Amazon.com*, Amazon.ca*, Amazon.com.au*, Amazon.co.jp*, Amazon.co.uk*, Amazon.de*, Amazon.es*, Amazon.fr*, Amazon.it*, Amazon.nl*, Amazon.pl*, Amazon.se*, Amazon.sg*
The USB 3.1 variant of the StarTech 2.5″ SATA adapter works well with the Pi 4. The USB 3.0 variant doesn’t have firmware updates available and is not recommended.
Links: Amazon.com*, Amazon.ca*, Amazon.com.au*, Amazon.co.jp*, Amazon.co.uk*, Amazon.de*, Amazon.es*, Amazon.fr*, Amazon.it*, Amazon.nl*, Amazon.pl*, Amazon.se*, Amazon.sg*
My project moves around but can fit a USB drive
Many USB drives are a poor choice for Pi storage media because they have very poor 4k random read / write performance. Micro SD cards are faster than a run of the mill / genreic flash drive.
That being said, with the new Raspberry Pi 4 the USB 3.0 bus is having really high end flash drives outperforming Micro SD cards. On the 3B+ and older boards without the new bus USB flash drives are usually not a good choice (even the good ones).
One drive that shows great performance even on a 3B+ is a special USB drive by SanDisk that is actually a solid state drive on a stick. It has the same size / dimensions of a regular flash drive but uses solid state storage internally giving it great 4k random read / write performance. I own it and it benchmarked at 2330 putting it more than double any MicroSD card and only a couple hundred points below Samsung Pro 2.5″ SSDs.
The SanDisk Extreme Pro USB SSD is a true solid state drive. This is different than a typical “flash drive” which uses extremely cheap memory and has very low random I/O performance/throughput compared to a real solid state drive. I’ve used both the USB 3.1 and USB 3.2 variants with the Pi successfully and they benchmark very well!
Links: AliExpress*, Amazon.com*, Amazon.ca*, Amazon.com.au*, Amazon.co.jp*, Amazon.co.uk*, Amazon.de*, Amazon.es*, Amazon.fr*, Amazon.it*, Amazon.nl*, Amazon.pl*, Amazon.se*, Amazon.sg*
My project is small form factor and can’t use USB adapters or storage
There’s lots of cool projects out there that using any type of USB attached storage is not an option. For these projects Micro SD is still king. The good news is that Micro SD has had some recent developments such as the A1 / A2 application class cards. A2 is not supported by Raspberry Pi yet (or almost anything else really) so A1 is the important mark to hit.
I’ll cover Micro SD in depth in the Micro SD analysis section but here is the current recommendation:
The SanDisk Extreme A1-A2 SD card has the best scoring SD card on Pi Benchmarks for years and is second in popularity only to the SanDisk Ultra (often included in combo kits). The application class (A1) means random I/O speeds (very important when running an OS) have to meet a higher standard. There’s no benefit on the Pi for A2 right now so get whichever is cheaper/available.
Links: AliExpress*, Amazon.com*, Amazon.ca*, Amazon.com.au*, Amazon.co.jp*, Amazon.co.uk*, Amazon.de*, Amazon.es*, Amazon.fr*, Amazon.it*, Amazon.nl*, Amazon.pl*, Amazon.se*, Amazon.sg*
The SanDisk Extreme A1 Application Class version continues to dominate other Micro SD cards on the benchmarking charts.
SSD Analysis
SSD benchmarking so far has shown that there is not much of a difference between an older cheap SSD like a outdated mSATA Hynix drive and top of the line drives like the Samsung 850 Pro. The difference from the oldest cheap drives and top of the line was only about 100 points.
This is because the Pi has a USB 2.0 bus. Even the slowest oldest SSDs are so fast that they hit the maximum possible data transfer rate over USB 2.0. Because of this it makes sense to buy the cheapest SSD drive possible that is still reliable. See my recommendations section for ideas.
Micro SD Analysis
The Micro SD market has always been a difficult place for Raspberry Pi owners. Since there traditionally was no classification that indicated random read / write performance we simply had to buy different cards and benchmark them.
The problem with that was that Micro SD manufacturing processes change. They can even change from batch to batch. The 2015 Samsung Evo cards were a good example of this. We found a card with amazing 4k random read / write performance but one day they changed their process and the new ones are not even close.
Fortunately things have recently improved for us somewhat because of, well, smartphones! Let’s talk about the application class.
Micro SD A1 / A2 Application Class
Application class cards were created because smartphones have become one of the top use cases for SD cards. Many people run applications directly off their SD card or have applications that keep their active storage on there. Tech savvy smartphone users sick of slow performing cards demanded a speed class was created to measure this type of performance.
This is great for us Pi owners because this type of use is 4k random reads / writes and is exactly the same as what we do on the Pi. Thank you smartphone owners!
It’s important to note that right now the Pi (and pretty much everything else) cannot currently make use of the new A2 standard as it requires special driver support to take advantage of the new features. I have benchmarked both the SanDisk Extreme and the SanDisk Extreme Pro A2 cards in my benchmark results and they did not perform any better than the A1 cards because of this.
Lets look at the application class performance features:
The new A1 application cards are fantastic and performing very well on the benchmark. So far every application card benchmarked has hit the minimum A1 targets. If you are looking for a better performing SD card then A1 is the way to go.
Video Class (V30, etc) and U Class (U1 and U3)
These don’t matter for the Pi. Basically at all. They are measurements for maximum sequential I/O throughput. For example if you have a video camera that needs to record in 4k it will need a very high sequential I/O maximum transfer rate.
The Pi depends on 4k block size random I/O as I’ve explained in earlier sections and these classifications don’t measure that. Indeed, my 3 worst performers on the benchmark are all U1 cards and got easily stomped (nearly doubled in score) by a SanDisk Ultra Class 10.
This doesn’t mean U capable cards are bad. The Samsung Pro+ is a U1 class card and performed incredibly well on the benchmark. It just means that the Samsung Pro+ has much higher quality memory / a better controller inside it.
The conclusion is that unlike the application class these classifications will not tell you if your card is going to be good or awful for the Pi. You need to benchmark them to know!
Picking the Fastest Micro SD Card
This can be difficult as manufacturers change their manufacturing processes and start using a different type of memory or on-board storage controller (likely to a cheaper one) for these cards. This can even happen on the same product line (such as the Samsung Evo) so manufacturer date is important when looking at these.
For example, the Samsung Evo+ was terrible a few years ago but more recent batches are scoring very well. The Samsung Evo “orange” older cards tend to be faster than the newer ones.
This is a big reason why I created this benchmark. With a bigger sample size of cards we as a community can pool our card benchmarks together and figure out which manufacturers and lines of cards are getting the good memory / on-board storage controllers.
Since manufacturers change their processes all the time to keep up we will need to watch the benchmark results and see where the “good stuff” is going and when the card quality quietly changes!
If you are currently in the market for a Micro SD card check the recommendations and the results table to see which current batches are performing the highest!
How you can contribute
The best way to help contribute to this research is to run the benchmark on your own Micro SD cards.
We are especially looking for the more unusual Micro SD card brands. Right now there are several manufacturers of Micro SD cards that have as yet to be identified. This information isn’t published anywhere publicly so the only way we can get them is through benchmarks submitted by you!
It is important to fill out everything you can see for the “Brand” question that comes up when you run the benchmark. Look at your card and fill in any branding markings you see.
This helps me identify unusual card vendors and add them to the script so they can be identified to help everyone compare between the different cards.
Conclusions
- Use a solid state drive (SSD) if possible. Instructions on how to set one up with the Pi are in this article
- SanDisk A1 application class cards are dominating the Micro SD results so far
- The only sensible Micro SD cards to buy right now are application class (A1) due to their outstanding 4k blocksize I/O performance vs. older cards.
- Micro SD card performance among the same brands and even the same models varied wildly depending on the manufacturing date. Memory quality and storage controller performance vary from batch to batch. Generally the newer they are the higher they tend to score on the benchmark as card technology is always improving.
- The Pi cannot utilize A2 so don’t pay extra for it (although sometimes the A2 versions are cheaper). A2 cards will run in A1 mode on the Pi.
- USB flash drives are terrible choices for Pi storage
- Old “spinny disk” 5400 RPM and 7200 RPM HDDs underperform decent Micro SD cards
With the new benchmark we should be able to learn a lot more about storage on the Pi. Micro SD cards seem to be the area we need to learn the most about. As more people run the benchmark we’ll continue to analyze and revise recommendations based on what everyone finds!
Hello,
I have a Qnine USB 3.1 Type-C to NVMe M.2 enclosure for a Western Digital WD Blue SN550 500GB and have it installed on my Raspberry Pi 4, connected to one of the USB 3.0 ports.
However, I don’t get great speed results, score around 2500, it goes slightly higher with quirks but it’s as though it’s connected to the USB 2.0 port:
Category Test Result
HDParm Disk Read 33.25 MB/s
HDParm Cached Disk Read 33.57 MB/s
Anyone else has this set u p ? If not, can anyone recommend another enclosure for the WD.
Thanks!
Giles
Hi, have’d use Berryboot for install a debian on iscsi device. Work good, it’s fast (rpi3). But How fast? Well, after a short search i got here.
Unfortunately the benchmark does not report all the values. Could you take a look and get him to cooperate? Tnx
Thanks for this, James. I’m a newcomer to this whole world with an idea of what I want. Your blog has been really helpful clarifying it all in tangible terms.
Question: what are your thoughts on something like the x825 expansion board like this:
Is there any reason to go this route vs. just using an adapter cable like you’ve been using? In theory, I like that it removes a cable sticking its ass out the back end of the pi, but that’s not a reason to do it.
Would love to hear your thoughts.
Tahnks!
Hey Mitch,
Great question! These are actually really popular on the storage benchmark. I’m still working on adding some better support for viewing which adapters are being used to the Pi Benchmarks tool but it’s definitely really popular and scores well on the benchmark!
Whether you like the form factor depends on what you are using the Pi for. In some cases having just a normal USB to SATA adapter works out well because you can put the hard drive in a corner somewhere out of the way and reduce the footprint of the Pi.
In applications where you were putting the Pi up on a shelf or stacking it somewhere the X825 really shines. This lets you use a full size 2.5″ drive and still have the Pi sitting stable on a flat surface without a large dangling USB adapter in the way. Overall it’s a great board for keeping a nice clean setup!
Is it possible to have the script working with external drive and not only boot drive ?
i have test a sandisk extreme pro 128 gb USB (SSD on USB 3) on raspberry pi 4 (1 gb) with exfat file system in extern “drive” mode and not in boot drive mode on archlinux arm and I have completly different results :
I have make all test from the mount directory of the ssd : tested in /mnt/ssd (my bootdrive is a SD card)
with your dd command (from storage.sh) :
dd if=/dev/zero of=test bs=4k count=80k conv=fsync 2>&1 => results in only 60 MB/s (exfat problem ?)
with dd if=/dev/zero of=test 64k=4k count=80k conv=fsync 2>&1 => results is 160 - 175 MB/s (much better)
hdparm -t /dev/sda : 328.69 MB/sec
fio4kRandWriteIOPS : fio --minimal --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=test --filename=test --bs=4k --iodepth=64 --size=80M --readwrite=randwrite | sed 's/;/!/g' | awk -F '!' '{print $49}'
9179
fio4kRandWriteSpeed :
fio --minimal --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=test --filename=test --bs=4k --iodepth=64 --size=80M --readwrite=randwrite | sed 's/;/!/g' | awk -F '!' '{print $48}'
36702
iozone : iozone -a -e -I -i 0 -i 1 -i 2 -s 80M -r 4k
random random
kB reclen write rewrite read reread read write
81920 4 59505 63432 97577 99012 44676 32405
so much better than results in the excel file, some of them with scores from 4562 to 3720 :
DD Write RandW IOPS RandR IOPS Rand Write Rand Read IO Read IO Write IO Rand Read IO Rand Write HDParm Disk
185 3053 3168 12212 12675 26757 23339 12402 12389 220,91
196 3033 3066 12132 12267 23467 21352 11166 11972 187,07
190 3080 3030 12320 12121 23331 20050 12151 11983 177,34
192 3097 2493 12389 9974 28206 18834 10289 11560 207,03
183 3098 2561 12395 10245 27773 25028 10327 11685 178,78
184 3103 3208 12412 12832 25887 23833 10091 11578 123,23
181 3125 2620 12503 10482 27059 25487 10132 11704 187,85
178 3098 3196 12394 12784 26056 23230 9940 11530 120,62
187 2918 2604 11672 10418 19565 17540 8743 11009 128,52
144 3005 2830 12022 11322 22968 19438 10998 12006 241,28
174 2912 2327 11651 9308 19461 16231 8571 10443 174,68
181 2882 2652 11529 10608 12503 10070 8439 10302 130,07
174 2884 2196 11539 8784 19245 12276 8395 10284 206,08
170 2914 2656 11659 10626 18557 16332 8383 10120 118,40
178 2949 2208 11797 8833 12451 10331 8495 10448 126,92
170 2920 2013 11682 8053 16990 9465 7610 11355 115,80
155 2498 2328 9992 9315 17143 15831 10254 11357 207,66
162 2545 3424 10181 13696 16082 14250 8532 10258 124,56
Ended up purchasing the recommended StarTech adapter using your Amazon link, and it works a little better benchmark-wise than all the other adapters and enclosures I have…especially that Sabrent – so bad.
I had to modify the script in two places to have it point to the right mountpoint/drive. But now I’m seeing good numbers. Makes me wonder what my numbers would be on the other controllers. I’ll try them out next.
MicroSD card (Samsung EVO+ 128GB) benchmark: 1392
PNY CS900 SSD (240GB) benchmark: 6093
In my case, a case with a nice fan, heatsinks on four chips, so the CPU/GPU temperature is hanging out right around 30°C. I’m also at the current/latest EEPROM and software.
Will share my findings on the other controllers with and without quirks.
Quick question: the recommended StarTech has the best features and does not need quirks enabled, right? That way I get all the features like TRIM or whatever? I feel like I’ve read that using quirks removes some features, but improves stability?
I’m glad I’ve been following your tutorials and guides. There’s such a HUGE difference between different controllers:
PNY CS900 240GB SSD on a RPi 4 using Apricorn SATA to USB 3.0 adapter NO Quirks (4183)
PNY CS900 240GB SSD on a RPi 4 using Apricorn SATA to USB 3.0 adapter WITH Quirks (4281)
PNY CS900 240GB SSD on a RPi 4 using ASMedia ASM1053 SATA to USB 3.0 adapter NO Quirks (4418)
PNY CS900 240GB SSD on a RPi 4 using ASMedia ASM1053 SATA to USB 3.0 adapter WITH Quirks (4275)
PNY CS900 240GB SSD on a RPi 4 using Sabrent SATA to USB 3.0 enc with JMicron JMS561U chipset NO Quirks (1396)
PNY CS900 240GB SSD on a RPi 4 using Sabrent SATA to USB 3.0 enc with JMicron JMS561U chipset WITH Quirks (4614)
PNY CS900 240GB SSD on a RPi 4 using recommended StarTech 2.5″ SATA to USB 3.0 adapter NO Quirks (6133)
PNY CS900 240GB SSD on a RPi 4 using recommended StarTech 2.5″ SATA to USB 3.0 adapter WITH Quirks (4476)
Samsung EVO+ 128GB MicroSD card on a RPi 4 (1425)
The SABRENT enclosure without Quirks enabled is worse than the on-board MicroSD card!
Hey Amarand,
This is an amazing writeup and definitely shows what I have been strongly suspecting: the adapter makes a HUGE performance difference, as you pointed out sometimes the difference between scoring less than a SD card and scoring 6000+!
I’ve been working on parsing more and more information on the adapters (which you can see on Pi Benchmarks and click the “Score” link for test details) and believe I’m pretty close to being able to create a page that compares the performance of the different adapters on the site as well. We have enough submissions that we should be able to break adapters down by performance using a few different metrics such as the average score of each adapter by drive. This should be particularly enlightening on something like the Kingston A400 which has hundreds of tests done on undoubtedly tons of different adapters!
This gives me more motivation to get that part of the site wrapped up and start displaying some basic data as I think there are people with some VERY nice drives out there running on poor performing adapters like the Sabrent.
I’m shocked at how many SATA to USB 3.0 adapters and enclosures I’ve went through – both with and without quirks – and I’m still only seeing 1400 score with a PNY SSD. That seems slow, seeing as I’m getting a 1000 score with my MicroSD Samsung EVO+ 128GB boot drive. Thoughts? I just ordered the StarTech you recommended, on Amazon, used your link so hopefully you get credit for that. Think it’ll just work? What numbers should I be seeing?
Hey Amarand,
Sorry I saw this a bit late but I’m glad you went with the StarTech!
I have an SSD attached with an adaptor, but I’m booting off the SD card (Pi4), how can I make this script test the USB/SSD drive instead of the sd card? It detects the other drive when it’s running, but it only ever benchmarks the SD card.
I have the same question. The script is only detecting the MicroSD card, and not looking at my /dev/sda (SSD in an enclosure with a SATA to USB 3.0 adapter). Partition /dev/sda1 is mounted.