4 ms·
This is interesting, but clearly there was caching going on, because the physical bus can't go as fast as some of these results. Samsung's own comments about th
by johnklos 4y ago
This is interesting, but clearly there was caching going on, because the physical bus can't go as fast as some of these results. Samsung's own comments about their drives:
To reach maximum read/write speeds of up to 1,050/1,000 MB/s, respectively,
the host device and connection cables must support USB 3.2 Gen 2 and the UASP mode must be enabled.
Timing cached reads: 2038 MB in 2.00 seconds = 1020.29 MB/sec
Timing buffered disk reads: 874 MB in 3.00 seconds = 291.21 MB/sec
Makes sense.
Timing cached reads: 35130 MB in 2.00 seconds = 17596.74 MB/sec
Timing buffered disk reads: 2620 MB in 3.02 seconds = 866.55 MB/sec
17 gigabytes a second? If I had to guess, the test was run more than once without flushing the (computer's memory) cache / being rebooted / being disconnected and reconnected.
- justsomehnguy 4y ago-T Perform timings of cache reads for benchmark and comparison purposes. For meaningful results, this operation should be repeated 2-3 times on an otherwise inactive system (no other active processes) with at least a couple of megabytes of free memory. *This displays the speed of reading directly from the Linux buffer cache without disk access. This measurement is essentially an indication of the throughput of the processor, cache, and memory of the system under test*.