Jump to content

CrystalDiskMark - What does each number mean for real world applications?

dark051128

There are 8 numbers in CrystalDiskMark, I wonder what does each of them mean for real world applications? Don't be that person that gives out meme answers like sequential read/write, queue depth, and all that blah blah blah. Which number matters if you are launching an application, recording a gameplay footage, editing photos and videos, etc?

 

Screenshot_4.png

Link to comment
Share on other sites

Link to post
Share on other sites

Sequential : performance in continuous file copy. ie. good for doing large file copy.

Random 4k : for processing multiple small files in different sectors / location.

The left on is for read performance and the other one is for write performance.

What ssd is that? this is a very good number.

 

read this:

https://www.thanalysis.com/2020/11/crystaldiskmark-and-interpretation-of-test-results.html

Ryzen 5700g @ 4.4ghz all cores | Asrock B550M Steel Legend | 3060 | 2x 16gb Micron E 2666 @ 4200mhz cl16 | 500gb WD SN750 | 12 TB HDD | Deepcool Gammax 400 w/ 2 delta 4000rpm push pull | Antec Neo Eco Zen 500w

Link to comment
Share on other sites

Link to post
Share on other sites

-- Moved to Storage Devices --

 

The top four numbers represent sequential speeds, both in read and write.

The bottom four numbers represent random speeds, both in read and write.

 

To first address read/write.

Read: reading a file, which would include opening a file, opening a program, starting your OS, etc.

Writing: when you are creating/editing a file and making new data to be saved.

 

Sequential vs. random.

Sequential is generally the simpler of the two, it's reading or writing data in a sequential pattern, one after the other.

Random read/write is when data may be found on different parts of the disk, so the controller needs to be able to find these different parts to read/write efficiently and fast.

The memory on the drive may be fast in sequential reads/writes, but if the controller can't keep up with the random requests, it may still prove slow in day-to-day use.

HDD's for example have 'okay' sequential performance, but really poor random performance, which generally makes them crappy as an OS/program drive.

 

The reason I say this, is because 'real life' work is often just not laid out in a sequential way, requiring the controller to find data/space all over the drive.

CrystalDiskMark also has small and large file tests, because a controller may perform differently with many small requests, compared to fewer large requests.

"SEQ1M", "SEQ128K". The '1M' and '128K' stand for 1MB and 128KB respectively, showing the sort of size files these tests use (although I don't know for sure if those are actually the sizes, I always just figured that was the case.

21 hours ago, dark051128 said:

launching an application

Read speeds, generally sequential, because the program is saved in one place.

21 hours ago, dark051128 said:

recording a gameplay footage

Write speeds, because you're saving a file. Generally sequential and large sizes, unless the controller has to 'find' free space some place else.

21 hours ago, dark051128 said:

editing photos and videos

These are both pretty intensive applications, for both reading and writing. Often sequential and random.

Mostly these would be sequentially read applications.

Reason I say this, is because when - for example - working on a video, it needs to load videos from some place else on the disk, in varying sizes and bitrates. These video clips may be saved in a different sort of format in the video editing program, to speed up the editing process, etc.

EDIT: I've been thinking a bit more on this. I think video editing especially so, is a mix of random and sequential read/write. A bit of everything really. I can't say it's more one thing vs. another.

 

If you want to figure out (or estimate really, it's not an exact science) if read/write and seq/random is important for the work, try thinking about what the program does.

Many small files, or few large ones? That would make you figure out if you should look at 1M or 128K for example.

Does it save data, or retrieve data? That would be write and read respectively

Is all the data in one place (generally), or not? sequential and random respectively.

 

But keep in mind, this is not an exact science, as it's pretty much impossible to figure out what is the most important for all programs. Plus, programs change over time too.

Puget Systems has some great tests, but from what I can see, they mostly have tests that compare different storage solutions (HDD vs. SATA SSD vs. PCIe/NVME SSD) and not in-depth in specific SSD's.

"We're all in this together, might as well be friends" Tom, Toonami.

 

mini eLiXiVy: my open source 65% mechanical PCB, a build log, PCB anatomy and discussing open source licenses: https://linustechtips.com/topic/1366493-elixivy-a-65-mechanical-keyboard-build-log-pcb-anatomy-and-how-i-open-sourced-this-project/

 

mini_cardboard: a 4% keyboard build log and how keyboards workhttps://linustechtips.com/topic/1328547-mini_cardboard-a-4-keyboard-build-log-and-how-keyboards-work/

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×