Closed benrubson closed 4 years ago
The receiving side is measuring the stats in 2 procs until the very end, so I disabled early stats except from the sender.
Thank you Wayne.
I've updated my post above with some Results, and, as you can see, issue is not only on receiver side, but also on sender side, where the --stats
numbers are wrong.
Instead of simply disabling the stats if / when they are wrong, do you think the accounting process could be modified in a manner that stats would be sort of "real-time" computed, so that when transfer is aborted, numbers are accurate, and available at both sides ?
Thank you again 👍
If you're killing processes with internal-only signals, you have to live with the fact that you get crap in the results since the stats info hasn't been updated by the end-of-run data updating. The only way to make (at least some of) the stats constantly updated is a total re-architecture of the 3-process layout, which is something that I'm contemplating for the future but won't happen any time soon.
Hi,
In some situations, especially when transfer is aborted, stats are wrongly computed, at both sides.
Here's an example of a
CTRL+C
interrupted transfer :Results : on receiver side,
sent
/received
numbers are wrong.And with
SIGUSR2
:Results : on receiver side,
sent
/received
numbers are wrong. Results : on sender side, many of the--stats
numbers are wrong.Thank you 👍