Open mbakholdina opened 4 years ago
Hi, Let me help this issue. These roadmaps are in progress?
Hi @OdaDaisuke, thank you for offering your help. Many statistics related improvements and issues need to be addressed carefully as they require API changes. We postponed major improvements to 1.5.1 release. If any help will be required, I'll let you know.
Hi @mbakholdina Since 1.5.1 has now been released and does not include any of this, do you have a new target for this issue ?
Hi @Fanfwe Will see. Might be included in v1.6.0 if time permits.
A table of currently present/missing stats
Revise and improve SRT stats API:
[ ] The calculation of accumulated (Total) statistic is not necessary, see issue #1232,
[ ] Add pktRcvDiscarded statistics for member sockets in a group to count packets that arrived on a path, but were discarded because they already exist in the receiver buffer (arrived over the other path).
[ ] Revise and improve
CBytePerfmon
structure,[ ] Revise
srt_bstats
andsrt_bistats
API functions to have only one function for retrieving SRT socket statistics, see issue #1213,[ ] Revise, improve and add missing statistics, see issues #1208, #1211, #1212, #1214, #1220, #1272, #1287, #1375, #1394,
[ ] Rename statistics: #1262, #1209,
[ ] Update the documentation, see issue #1207,
[x] Add absolute timestamp when collecting SRT statistics in
srt-live-transmit
, see issue #1218,[ ]
-s
option insrt-live-transmit
gives statistics eachs
packets. Change to milliseconds instead of packets or better add an option how to collect statistics: per number of packets or each xx milliseconds. See issue #1058,[ ] Consider whether we are going to implement the following FRs: #902, #1122, #908
[ ] mbpsSendRate, mbpsRecvRate interval #1812
[ ] #900
[ ] #2177.
[ ] Calculate the number of packets that arrived before the TSBPD timeout. This statistic should be decoupled from the jitter on UDP input and reading from the SRT socket to highlight the network performance and SRT configuration efficiency.