Direct-Attached Storage Benchmarks - Samsung Portable SSD T3 Review

Synthetic Benchmarks - ATTO and Crystal DiskMark

Samsung claims sequential read and write speeds of up to 450 MBps, and these are backed up by the ATTO benchmarks provided below. Unfortunately, these access traces are not very common in real-life scenarios.

CrystalDiskMark, despite being a canned benchmark, provides a better estimate of the performance range with a selected set of numbers. As evident from the screenshot below, the performance can dip to as low as 20.68 MBps for random 4K reads. The presence of DRAM helps boost the performance quite a bit.

Benchmarks - robocopy and PCMark 8 Storage Bench

Our testing methodology for DAS units also takes into consideration the usual use-case for such devices. The most common usage scenario is transfer of large amounts of photos and videos to and from the unit. The minor usage scenario is importing files directly off the DAS into a multimedia editing program such as Adobe Photoshop.

In order to tackle the first use-case, we created three test folders with the following characteristics:

• Photos: 15.6 GB collection of 4320 photos (RAW as well as JPEGs) in 61 sub-folders
• Videos: 16.1 GB collection of 244 videos (MP4 as well as MOVs) in 6 sub-folders
• BR: 10.7 GB Blu-ray folder structure of the IDT Benchmark Blu-ray (the same that we use in our robocopy tests for NAS systems)

In almost all the cases, we find that the performance of the T3 slightly lags the performance of the T1. However, it is still faster than most other SSDs behind a SATA - USB bridge chip.

For the second use-case, we take advantage of PC Mark 8's storage bench. The storage workload involves games as well as multimedia editing applications. The command line version allows us to cherry-pick storage traces to run on a target drive. We chose the following traces.

• Adobe Photoshop (Light)
• Adobe Photoshop (Heavy)
• Adobe After Effects
• Adobe Illustrator

Usually, PC Mark 8 reports time to complete the trace, but the detailed log report has the read and write bandwidth figures which we present in our performance graphs. Note that the bandwidth number reported in the results don't involve idle time compression. Results might appear low, but that is part of the workload characteristic. Note that the same testbed is being used for all DAS units. Therefore, comparing the numbers for each trace should be possible across different DAS units. These benchmarks also point to the T3 being slightly behind T1 in performance.

ncG1vNJzZmivp6x7orrAp5utnZOde6S7zGiqoaenZH5xfJRwZqyZnajCr7OMqaarrJGXuaZ50qybZqxjYr%2Bmwsiermhr