SSDBoss Review Our evaluation of MX300 vs M500

read performance

How quickly data is read from the drive

4K Random Read, 4K Random Read Access Time and 512K Sequential Read

write performance

How quickly data is written to the drive

4K Random Write, 4K Random Write Access Time and 512K Sequential Write

real world benchmarks

How well the drive performs common tasks

Photoshop Lens Filter and AS SSD ISO Copy

Benchmarks

How well the drive performs on common benchmarks

PCMark Vantage and AS SSD Score

No winner declared

Too close to call

Differences What are the advantages of each

Front view of Crucial MX300

Reasons to consider the
Crucial MX300

Report a correction
Faster 4k random read 244.23 MB/s vs 126.46 MB/s Around 95% faster 4k random read
Higher PCMark vantage score 30,438 pts vs 24,678 pts Around 25% higher PCMark vantage score
Faster 512K sequential write 477.46 MB/s vs 413.32 MB/s More than 15% faster 512K sequential write
Significantly faster photoshop lens filter 51.6 s vs 57.4 s More than 10% faster photoshop lens filter
Lower 4k random read access time 1.02 ms vs 1.98 ms Around 50% lower 4k random read access time
Faster AS SSD ISO copy 437.34 MB/s vs 306.5 MB/s Around 45% faster AS SSD ISO copy
Lower avg. power consumption 1.92 Watts vs 2.13 Watts Around 10% lower avg. power consumption
Front view of Crucial M500

Reasons to consider the
Crucial M500

Report a correction
Higher capacity 960 GB vs 750 GB Around 30% higher capacity
Faster 4k random write 66.2 MB/s vs 44.94 MB/s More than 45% faster 4k random write
Significantly lower 4k random write access time 3.78 ms vs 5.56 ms More than 30% lower 4k random write access time

Benchmarks Real world tests of MX300 vs M500

4K Random Read

MX300
244.23 MB/s
Crucial M500
126.46 MB/s

4K Random Write

MX300
44.94 MB/s
Crucial M500
66.2 MB/s

Avg. Power Consumption

MX300
1.92 Watts
Crucial M500
2.13 Watts

4K Random Read Access Time

MX300
5.56 ms
Crucial M500
3.78 ms

4K Random Write Access Time

MX300
1.02 ms
Crucial M500
1.98 ms

Comments

comments powered by Disqus