Send video stats and webrtc internals sump from device Spring and desktop: 
https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/610858/

Apprtc loopback calls also shows low FrameRateInput and FrameRateSent in send video stats

srcv@
a) In the last known good test run on the Spring, what kind of googFrameRateInput were you seeing?
b) Can you get a webrtc-internals dump of a loopback call? The screenshot, while helpful, doesn't include enough data for a deeper investigation.

niklase@ - do you have any ideas? The screenshot of the loopback call looks especially strange not only because of the low googFrameRateInput, but also the drops in googFrame[Height|Width]Sent relative to googFrame[Height|Width]Input.

The drop in sent resolution is nothing strange, it's CPU adaptation kicking in and dropping the resolution. You can see the corresponding changes in 'googCPUAdaptation' at the top right corner (title cropped out).

The input frame rate is strange, since that indicates that the camera only delivers 8 fps.

> it's CPU adaptation kicking in and dropping the resolution.
Hmm, it's a bit worrisome that CPU adaptation would trigger in a loopback call. But for now, let's focus this bug on the low googFrameRateInput.

Assigning to srcv@ to answer the questions in #3.

> Hmm, it's a bit worrisome that CPU adaptation would trigger in a loopback call.

Why? A loopback call uses more or less exactly the same CPU as a normal call.

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

tnakamura@:
WebRTC internal dumps for AppRTC peer2peer calls on device Spring were attached in comment#1


Tested apprtc calls and hangouts on device Spring with following builds:
M52 52.0.2743.32 / 8350.21.0 beta
M51 51.0.2704.79 / 8172.47.0 stable and 
M50 50.0.2661.104 / 7978.76.0 stable

- Send(video) googFrameRateInput and googFrameRateSent are around 6-8 fps throughout the calls
- Removing "Regression" label
- WebRTC internal dumps from AppRTC loopback calls on device Spring with latest M52 beta (52.0.2743.32 / 8350.21.0): https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/610858/ 

jansson@, can you take a look?

To me it looks like a CPU issue, have you tried H264 or VP8? VP9 uses quite a lot more CPU than the aforementioned codecs.

Yes. This issue is also seen with H264 and VP8 on device Spring

Added WebRTC-internal dumps from device Spring with vp8 and h264 to this link:
https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/610858/

I wonder if this is related to http://crosbug.com/p/52823. jansson@ What's the next step? Spring is using sw encode for vp8 and h264.

Yes it does sound like that could be the issue since it's affecting those devices. Next step I guess is to figure out the cause in  http://crosbug.com/p/52823. Assigning to niklase@ to mirror the cros bug.

This issue is Pri-1 but has already been moved once. Lowering the priority and moving to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

posciak@ will this make it to M54?

Removing milestone as there was no work for this done for 54, and this is not a regression per above reports.

Were we able to identify if this is related to http://crosbug.com/p/52823? What is the resolution used in these tests?

Reduced camera resolution from 1280 x 720 (camera resolution used in intial bug test report) to 640 x 360 (device supported camera resoltuion) and tested apprtc loopback and peer2peer calls on chrome device Spring with M56 56.0.2924.53 / 9000.50.0 beta

Camera resolution used for tests : 640 x 360
Network: Connected to Ethernet

Send Video FrameRateInput and FrameRateSent for :
1.Apprtc loopback:

a) VP9:
FrameRateInput: First 1min 5 fps and later 20 fps
FrameRateSent: First 1 min 3-5 fps and later 20 fps

b) VP8:
FrameRateInput: 15-20 fps
FrameRateSent: 15-20 fps

c) H264:
FrameRateInput: 1min 5-15 fps and later 20 fps
FrameRateSent: 1min 5-15 fps and later 20 fps

2. Apprtc peer2peer:

VP9:
FrameRateInput: 1min 1-10 fps later 10-20 fps
FrameRateSent: 1min 2-6 fps later 10-15 fps

VP8:
FrameRateInput: 2-10 fps later 15-20 fps
FrameRateSent:2- 5 fps later 10-20 fps

H264:
FrameRateInput: 10-25 fps
FrameRateSent: 10-25 fps

WebRTC internal dumps for apprtc loopback and peer2peer calls on device Spring:
https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/610858/Spring%20Apprtc%20calls%20Webrtc%20internal%20dumps%20M56%20beta/


P.S : Apprtc call send video FrameRateInput and FrameRateSent are not very low as mentioned in the initial bug report.

niklase@ / posciak@ : Please suggest if these apprtc framerates are acceptable for device Spring.

Activating. Please assign to the right owner and the appropriate priority.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Ping for triaging.

Archiving. Please reopen if this is still an issue.