Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Benchmarks question: what is copying time? #19

Closed
vi opened this issue Jul 12, 2021 · 1 comment
Closed

Benchmarks question: what is copying time? #19

vi opened this issue Jul 12, 2021 · 1 comment

Comments

@vi
Copy link

vi commented Jul 12, 2021

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
Copy link
Owner

  • 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants