search

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

[Feature] A progress meter would be nice #35

Open zachriggle opened 2 years ago

zachriggle commented 2 years ago

Currently fcp is a "do one thing, do it well" tool, but it lacks a lot of introspection.

It would be nice if there were a --progress flag that printed out the number of files / bytes copied per second, so that one could gauge how fast a copy is performing.

zachriggle commented 1 year ago

Following up on this, I would love to sponsor you or this project, @Svetlitski. Would it be useful to offer a $20 bounty and $5/month sponsorship to get this implemented? I don't mind hiding it behind a --progress or --verbose flag so that current behavior doesn't change.

Svetlitski commented 1 year ago

While I sincerely appreciate the offer, I must decline the offer of any kind of sponsorship, since I work on this in my spare time and would otherwise feel obligated to invest more time in it.

As for a progress meter, that's certainly a possibility. My only hesitancy is that any kind of progress meter will impose a small performance penalty, but given that fcp is otherwise completely IO-bound, I imagine this would be insignificant. Nonetheless, it's something I'd like to benchmark just to be safe. This should be pretty easy overall though, and I need to release an update with some minor fixes and dependency updates anyway, so yeah sure, I'll take a look.