Raspberry Pi Storage Benchmarks + Benchmarking Script

Pi Benchmark 2019 Contenders
Pi Benchmarks 2019 Contenders

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!


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


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)


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:

Kingston A400 SSD
Kingston A400 2.5″ SATA SSD

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*

StarTech 2.5" SATA to USB 3.0/3.1 Adapter
StarTech 2.5″ SATA to USB 3.1 Adapter

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.

SanDisk Extreme Pro USB SSD
SanDisk Extreme Pro SSD

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:

SanDisk Extreme A1
SanDisk Extreme A1

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:

Application Class Performance Chart
Application Class Performance Chart

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.


  • 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!


Inline Feedbacks
View all comments

2 years ago

benchmark graph/table is missing

also it would be nice if you made you benchmark site searchable, sortable etc. It’s hard to find a drive at the moment and cannot sort in any way.

For example portable is useless now, it just ahs a list of the top same drive over and over in SSD. how do I find USB pendrives, or a specific type to get the data.
I think it’s got a bit bigger than it started 😉

Very useful though just can’t get to the data.

Jim "JR"
Jim "JR"
2 years ago

A few other things:

1. How do I test something other than the SD drive the system is running from? (i.e. I want to plug in a SSD via USB-3 and test it, etc.)

As it is, this test seems to automagically test the primary root device, like it or not.

Note that this has been mentioned before and, as of yet, I have not seen an answer.

2. How do I *NOT* submit results? (i.e. I’m figuring out how to use this thing, or haven’t looked at the brand/spec of the device I’m testing.)

3. Are the resultant scripts resident on my device? (so that i can re-run them, or offer modifications.)

Jim Harris
Jim Harris
2 years ago

I have now dug up a Pi-4 (4 gig) in a 7″ display enclosure tgat I can pop-out and use for these metrics.

This leaves me with one last question that is not answered in your (otherwise excellent!) article anywhere:

What is the configuration/setup required to run the test?

In other words, if I want to benchmark a particular SD card, do I use a USB to SD adapter? Do I have to load up Buster on every single card I want to test and boot from each and every one so that it runs “natively”?

If my tests are going to be even CLOSE to valid, I need to test the exact same way you are. Otherwise, my tests are going to be waaay over HERE while your tests are waaaay over THERE, and nobody will be able to tell why.

I’d much rather know that *before* I start testing if I am going to have to disassemble my system and clone a s-load of cards.

Thanks again for all your help, and for an excellent article!

Jim “JR”

Jim "JR"
Jim "JR"
2 years ago

Phenomenal article! I know I will be linking to it from some other blogs I haunt where this question is constantly arising.

My primary use for the Pi, (at least right now), is as a robotics platform using the Dexter GoPiGo, a great robot with an excellent on-line community.

What I would like to do is, somehow or other, “pre-qualify” devices using your standard, but without digging up a Pi and hooking it up just to use as a test bed. I would like to be able to set up the device via USB on either Windows (10) or Linux (Mint, 18+) and test various configurations of adapter and/or device. Now, obviously this would not be “exactly” like the Pi, but hopefully would allow me to exclude obvious punters and wannabees before testing on the Pi itself.

Is this possible somehow?


Jim "JR"
Jim "JR"
2 years ago

I will try that. (Using the script on Mint)

Just for grins and giggles, I downloaded the Crystal DiskMark 7.0 (stand-alone) drive benchmark and ran it on a few devices I have.

Trying to make it as “similar” to the Pi as possible, I limited the tests to four queues and four threads / one queue and one thread. (It wanted 32 queues and a zillion threads. . .)

I am curious as to how similar this is to the testing you’ve seen – is this a reasonably accurate model?

I tested:
An older OEM Samsung 128 GB SSD
An older OEM Seagate Momentus 160 GB HDD
A Micro Center branded 128 GB USB 3.0 flash drive just for the heck of it.

Results: (Compiled from several DiskMark result reports)

CrystalDiskMark 7.0.0 x64 (C) 2007-2019 hiyohiyo

* MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]
* KB = 1000 bytes, KiB = 1024 bytes

Profile: Default
Test: 1 GiB (x5) [Interval: 5 sec]
Date: 2020/09/27 11:57:20
OS: Windows 10 Professional [10.0 Build 18363] (x64)
System: HP EliteBook 8570p with 16 GB Crucial DDR3 RAM with an i7 processor running at 2.7 gHz.

All drives were tested twice using 4K random writes to a 1 gig file:
1. Four queues – four threads
2. One queue – one thread

Both the SSD and the HDD were tested using the USB 3.0-SATA interface card
from an un-branded 2.5″ drive enclosure using an InitIO interface chip.

All devices were tested using the same USB 3.n port on my laptop.

Sequential tests were not performed.


Samsung 2.5″ 128GB SSD
Model MZ-7PC1280/0H1

Random 4KiB (Q= 4, T= 4): 15.925 MB/s [ 3887.9 IOPS]
Random 4KiB (Q= 1, T= 1): 6.449 MB/s [ 1574.5 IOPS]

Random 4KiB (Q= 4, T= 4): 13.459 MB/s [ 3285.9 IOPS]
Random 4KiB (Q= 1, T= 1): 8.406 MB/s [ 2052.2 IOPS]


Seagate Momentus 160GB HDD
Model 5400.3

Random 4KiB (Q= 4, T= 4): 0.732 MB/s [ 178.7 IOPS]
Random 4KiB (Q= 1, T= 1): 0.432 MB/s [ 105.5 IOPS]

Random 4KiB (Q= 4, T= 4): 0.583 MB/s [ 142.3 IOPS]
Random 4KiB (Q= 1, T= 1): 0.536 MB/s [ 130.9 IOPS]


Micro Center store branded USB 3.0 128GB USB flash drive

Random 4KiB (Q= 4, T= 4): 6.780 MB/s [ 1655.3 IOPS]
Random 4KiB (Q= 1, T= 1): 5.087 MB/s [ 1241.9 IOPS]

Random 4KiB (Q= 4, T= 4): 0.009 MB/s [ 2.2 IOPS]
Random 4KiB (Q= 1, T= 1): 0.016 MB/s [ 3.9 IOPS]


1. As expected, the SSD, (even though a cheap drive included in the OEM install), absolutely CRUSHED everything else in sight.

2. The Seagate Momentus HDD performance was much worse than I expected.

3. The Micro Center Flash Drive actually posted respectable read numbers, though the write numbers STINK – which I expected, based on previous experience reading and writing to the device.

Bonus Test!

I accidentally ran one test without changing the drive from the default C: drive – a top-end, (at the time), Crucial MX-300 series 2T SSD that set me back many hundreds of dollars when I bought it. I thought I was testing the Seagate HDD and I said to myself, “Darn! I didn’t expect those numbers to be THAT high. . .”


Crucial MX-300 2 TB SSD on the laptop’s internal SATA interface with all the special drivers and enhancements installed:

Random 4KiB (Q= 4, T= 4): 343.247 MB/s [ 83800.5 IOPS]
Random 4KiB (Q= 1, T= 1): 19.176 MB/s [ 4681.6 IOPS]

Random 4KiB (Q= 4, T= 4): 330.630 MB/s [ 80720.2 IOPS]
Random 4KiB (Q= 1, T= 1): 54.967 MB/s [ 13419.7 IOPS]

Jim "JR"
Jim "JR"
2 years ago
Reply to  Jim "JR"

One other thing that I forgot to mention – which can be especially relevant if you’re using the Pi in a remote/battery-operated configuration:

SSD drives are almost as power-hungry as their 3.25″ “full size” mechanical brothers.

For comparison:
* My Samsung 2.5″, 128 GB SSD has a rated current draw of *1.5 amps*, all by it’s little lonesome, as specified by the label on the drive itself.

* The Seagate 2.5″ 160 GB “spinny disk” hard drive has a rated nominal current draw of only half an amp, (0.487 amps), with a “you gotta be KILLING me!” absolute maximum of one ampere, as specified by Seagate’s data sheet for the drive series.

As much as I’d LOVE to use something like that SSD on my GoPiGo robot, it would crush my ‘bot’s battery life faster than a spinning 3D LIDAR ranging/mapping array would!

2 years ago

This is a great tool, thank you for the hard work!

I wanted to post to make sure you know the website SSL cert expired on 5/23/2020. It can be bypassed in Chromium browsers but Firefox blocks it completely.

Jon Robertson
Jon Robertson
2 years ago

I ran your benchmark on my SD card four days ago (May 17th) and found the results of that benchmark on your site (both old and new). Today, I added a SN750 to my Pi, copied the SD to it, and set the SN750 as root. Then I rebooted and ran your benchmark again.

I can’t find my new benchmark on either site. I didn’t use the same “note” or “alias” for the second benchmark. Any idea why the new benchmark isn’t showing up?

2 years ago

For those who are on HASS.IO I’ve created a wrapper – add-on:
I had to apply two changes to the script – no publishing of results + BootDrive detection to go search mounted device in tree: $(findmnt -nvoSOURCE -T “$ChosenPartition”)