Webrtc & GPU

[Sots Ts]

Hello,

We are trying to optimize the Windows laptop hardware experience with webrtc 1920x1080 4mbps @30fps streams with 10 peers in a session on Chrome.

We see the CPUs get pretty utilized, can anyone please guide me to a best place to learn about offloading any part of this to the GPU?

If anyone can comment on using the GPU vs CPU and perhaps GPU acceleration with webrtc & Chrome that would be appreciated also.

Thanks!

[Sots Ts]

...we're using webm/h264 btw

[ArtyC]

Hello, please name the spec range of laptops you're working with.

[Sots Ts]

Thank you Arty.

We are using Asus laptops with:
16GB RAM

CPU AMD Ryzen 9 - 6900HS

GPU AMD Radeon RX 6700S

To be more precise about the webrtc scenario with max 10 peers in a session, one "university teacher peer" would be sending 2 streams, the other parties all send one stream: 

- each peer pushes lo-med-hi simulcast (250-750-3000=4000kbps total) to Janus; each subscriber thus is receiving only a single 3000kbps remote peer stream (the other 8 peers received would be @ 250kbps each)... ~4750kbps total received

- each peer is thus sending 4000kbps total of 30fps/1920x1080/webm h264

- the main "teacher" peer is thus sending 4000kbps X 2= 8000kbps to Janus --> this is the peer whose local machine we want to leverage GPU (not CPU) if that reduces CPU load and if that may have other positive benefits

 

[Harald Alvestrand]

Have you tried flipping through the codecs available to see if some codecs are more efficient than others?
I think the degree to which encoding is HW-backed varies between codecs and between platforms.

--
This list falls under the WebRTC Code of Conduct - https://webrtc.org/support/code-of-conduct.
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/284b8de1-6c01-432b-a53c-64efb5ab452en%40googlegroups.com.