Closed Bug 1330587 Opened 7 years ago Closed 7 years ago

framerate in webrtc getStats report does not change timely

Categories

(Core :: WebRTC: Networking, defect)

50 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1348657

People

(Reporter: shuquan825, Unassigned)

References

Details

(Whiteboard: [needinfo reporter 1/13/17])

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Steps to reproduce:

1. make a video call
2. limit bandwidth using tools like Netbalancer, monitor video quality and frameRate change in getStats report
3. recover the bandwidth to good condition, monitor again


Actual results:

when video becomes very slack, the framerate still keep big value for a long time sometimes several minutes.
when network recovers from bad to good situation, the video is very fluent, but the framerate still keep low value like 3~5 fps for a long time.

Compare with Chrome, it will change timely.


Expected results:

framerate should reflect video fluency.
Component: Untriaged → WebRTC: Networking
Product: Firefox → Core
I guess this is because we're reporting the average for the entirety of the call, but as far as I can tell this statistic isn't part of the specification anyway.

jib?
Flags: needinfo?(jib)
Whiteboard: [needinfo jib 1/12/17]
Yes, hence the stat names frameRateMean and frameRateStdDev. - https://jsfiddle.net/ec9ossmu/

These were never in the spec, and we never prefixed them. See bug 951496 comment 32.
Flags: needinfo?(jib)
It's a rolling average as I recall.
What stat are you looking at in Chrome?
Flags: needinfo?(shuquan825)
aha. Looking at that bug I think we wanted to report them for our own use in Telemetry and about:webrtc.  Then after Olli's comment, we un-prefixed them.
And Steven Lee from comment 5 there: 
> After discussing with CJ, I added some more statistics data, standard deviation, minimum and maximum values.
Flags: needinfo?(shuquan825)
Whiteboard: [needinfo jib 1/12/17] → [needinfo reporter 1/13/17]
Please use new standard framesEncoded available in Firefox 55 instead. See bug 1348657 comment 23 for a demo.

I've filed bug 1367562 to remove these two stats.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.