Benchmarks question: what is copying time?

Svetlitski / fcp

A significantly faster alternative to the classic Unix cp(1) command, copying large files and directories in a fraction of the time.

BSD 3-Clause "New" or "Revised" License

734 stars 17 forks source link

Benchmarks question: what is copying time? #19

Closed vi closed 2 years ago

vi commented 2 years ago

Benchmark plots show some time period in seconds.

What does that time mean? The time between CLI tool start and when it exits? Or the time when copying actually finishes under the hood (so e.g. removable storage can be ejected)?

Also were benchmarks performed hot (when involved data was already in RAM) or cold (e.g. like after Mac analogue of /proc/sys/vm/drop_caches, if it exists)?

Also how benchmarks look with NFS or removable storage?

Svetlitski commented 2 years ago

The benchmarks measure copy time as the time between when the CLI tool starts and when it exits, as this is the metric which is most important to the average user.
The caches were warmed up prior to measurement, and left hot through the course of all runs. Feel free to peruse the benchmark code for more details.
Per the README, fcp is optimized for systems with an SSD. I have not profiled the tool when used with NFS or removable storage.