Closed Bug 976669 Opened 7 years ago Closed 2 months ago

about:webrtc should show running kbps speeds each stream (and auto-update)


(Core :: WebRTC, defect, P3)




Tracking Status
firefox80 --- fixed
Blocking Flags:


(Reporter: jib, Assigned: dminor)


(Blocks 1 open bug)



(3 files)

Some feedback in Bug 904622 suggests that our current about:webrtc page, which does not auto-update nor show kbps speeds for each stream, should do those things.

Useres are comparing it to chrome://webrtc-internals, and I think there are two components to that:

 1) More information and live updating information (this bug)
 2) Nice graphs.

In particular, send and receive rates may be calculated today from existing stats over time, like the attached page shows.

One solution would be to crib from the attachment, if it is fast enough. If not, (or if we decided not to auto-update for some reason) we could look at calculating speeds internally.
I should point out that I've tried auto-update, and it can be frustratingly janky. Also, we have to be careful not to wipe out the last-known stats for PCs when we refresh, or it will make diagnosing failed calls a bit difficult.
Have we tried auto-update since your rewrite? Perhaps there's less overhead now.

We'll need to break down what expectations are. For comparison, Google's webrtc-internals page appears to be a pure monitor in that it goes blank once the call ends (or tab closes, I cannot tell with apprtc), with a download button for loggy stuff.
(In reply to Jan-Ivar Bruaroey [:jib] from comment #2)
> Have we tried auto-update since your rewrite? Perhaps there's less overhead
> now.

I have not tried again, no. I would be pretty surprised if the rewrite helps with this in any significant way; we're talking about a pretty small amount of data.
Priority: -- → P2
Target Milestone: --- → mozilla33
Priority: P2 → P3
Target Milestone: mozilla33 → mozilla35
backlog: --- → webRTC+
Rank: 35
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Blocks: 1624328
See Also: → 1651757
Assignee: nobody → dminor
Severity: normal → S3
Priority: P4 → P3

This would be improved by smoothing the values a bit, but I'm not sure that is
worth the extra complexity at this point. I left out the remote values because
they do not update regularly, but with smoothing, we might be able to
include them as well.

Depends on D83317

Pushed by
Automatically update ICE and RTP stats; r=ng
Estimate bitrate for local streams; r=ng
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: mozilla35 → mozilla80
QA Whiteboard: [qa-80b-p2]
You need to log in before you can comment on or make changes to this bug.