Actions
Bug #4437
closedndncatchunks: confusing summary output (packet loss)
Start date:
Due date:
% Done:
100%
Estimated time:
Description
Here is an example of a ndncatchunks summary:
All segments have been received.
Time elapsed: 4984.3 milliseconds
Total # of segments received: 23676
Total size: 104174kB
Goodput: 167.203002 Mbit/s
Total # of packet loss events: 1
Packet loss rate: 4.22369e-05
Total # of retransmitted segments: 1789
Total # of received congestion marks: 50
RTT min/avg/max = 0.877/87.216/634.587 ms
However, the statistics about packet loss are confusing. The actual number of lost packets are 1789, thus the loss rate is 7.56%.
Proposed solution:
- Write "Total # of packet loss: 1789 (which caused 1 window decrease)"
- "Packet loss rate" should be calculated by actual number of lost packets, not "loss events" (window decreases)
- Keep # of retx, as they may differ from the packet loss count.
Updated by Anonymous over 6 years ago
- Related to Feature #4421: ndncatchunks: print summary by default added
Updated by Davide Pesavento about 6 years ago
- Status changed from New to Code review
- Assignee set to Chavoosh Ghasemi
- Start date deleted (
01/08/2018)
Updated by Davide Pesavento about 6 years ago
- Status changed from Code review to Closed
- % Done changed from 0 to 100
Actions