1300315 - FF WebRTC : AppRTC with VP8 taking more cpu and memory compared to h264 on mac

Status: RESOLVED INCOMPLETE

(Core :: WebRTC, defect)

Description

[KIshor Kulkarni]

Attachment: AppRTC with H.264 and VP8 codecs.docx

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

Steps to reproduce:

Run the calls with AppRTC webrtc solution with H.264 and VP8 codecs on the mac


Actual results:

Observed the AppRTC calls with the VP8 codecs taking more CPU and Memory than the AppRTC calls with the H.264 codec


Expected results:

It would have taken the same amount of cpu and memory as the H.264


Please find the details of the testing in the attached document , which compares the cpu and memory usage for the H.264 and VP8 codecs on the chrome and firefox on the windows and mac

Comment 1

[Paul Adenot (:padenot)]

Nils, jesup, is that something, that is expected for now ?

Comment 2

[Randell Jesup [:jesup] (needinfo me)]

The difference isn't that large.  And memory usage readings have very little to do with the codecs; most of the usage is the browser in general and in how it's reported.

What did you use to collect these stats?  What application was being used - just plain apprtc?  What machine configurations were used, and what OS versions?  What Firefox and Chrome versions?

What resolution video was each side sending, and what framerate?  (Chrome webrtc-internals will show you sent and received resolution and framerate; about:webrtc on firefox will show received and sent framerates.)

While firefox uses libvpx, the version chrome is using may be more recent.  We do update it reasonably often.

Thanks!

Moving back to unconfirmed for now

Comment 3

[Nils Ohlmeier [:drno]]

To add to Randell's questions: are the numbers the average from multiple runs? If so how many runs?

As you can see from Mozilla's own attempts to record memory usage here https://www.areweslimyet.com/faq.htm#how-is-this-data-generated this is not easy task.

What does "Half Duplex" and "Full Duplex" mean in this context? I'm assuming Half Duplex means that video was only send in one direction, but not the other, but are the numbers for receiving or for the sending side?

In the attached word document you highlight in red Firefox CPU usage on Mac with VP8 being 34.9%, which is 5% higher then the 29.9% with H.264. But on the other hand in your table the number for Firefox full duplex on Windows increases almost 7% from 22.9% to 29.6%.

Comment 4

[Nils Ohlmeier [:drno]]

Nothing actionable here.