When running a check command progress is tracked in how many checks are made and how much time has passed, as in, progress is purely per file, I'd love to see how much total combined filesize has been checked though as well.
Example of what it looks like:
Transferred: 0 B / 0 B, -, 0 B/s, ETA -
Errors: 4 (retrying may help)
Checks: 304753 / 304761, 100%
Elapsed time: 22h58m0.0s
What I'd love to see perhaps optionally perhaps always below Checks: could be something like dataprocesssofar:
Why? Well.... If I have a ton of tiny files I might want checkers --32 and if I have a ton of large files I might checkers --4 furthermore I might be scanning a million files but the first 100,000 are all large and next 900,000 are all small.... knowing how much size is being processed would better let me gauge when the command would finish, as well as, in hindsight at least, let me know if I set --checkers too low or too high.
Alternatively, but likely much more difficulty..... dynamic --checkers would be funky but possibly efficient? Something like --checkers 4 EXCEPT when detecting files below 1megabyte in size allow for them to occupy additional --checkers slots up to 20.... the problem being.... this is likely a paradox right? By the time rclone knows how large a file is, the operating system overhead has already been paid, right? So, I suppose this is only a problem that can be solved in hindsight? Maybe?
Sorry if this makes no sense, I'm in a rather unique situation. I'm migrating all my local data from one HDD to another, I used robocopy to copy it, but I'm using rclone to check the hashes of every single file before I unplug the old HDD entirely, and I have no clue if I should set --checkers to 4 or 8 or 12 or 24 because the HDD has lots of small and lots of large files. It took about two days to transfer all the files but the rclone check command looks like it will take four or five days, but the bottleneck appears to be the HDD not the hash calculations.
Sorry if this feature is foolish, I just thought it'd be cool 