Scaling of Transcoder

[cjagadis]

We tried the transcoder with a Single CPU (1.6 GHz, 3.75 GB) and one 480P RTMP Stream. It was CPU bound with 100% usage. And then next we tried with 4 core CPU (1.6 GHz, 3.75 GB) with 4 480P Streams and the CPU usage was again 100% for the transcoder. Does the transcoder scale linearly? The output to the player was pretty bad with 4 RTMP Stream and we were unable to get the streams to the player. If we just sent a single stream (single CPU), the behavior is perfect but CPU usage is 100%.

Any ideas on how to scale the transcoder? We always try to scale with the cheapest servers on GCP Compute Engine for we know to manage allocation/deallocation at a massive scale.

BTW, can we avoid transcoding if we stream RTMP with H264, OPUS? If we stream this, my hope is you can extract H264/OPUS and no transcoding is required for webRTC. Does this make sense?

I do appreciate your help in advance.

[Keukhan]

Hello, @cjagadis

Transcoding requires a lot of CPU performance. So, It's expensive in a GCP environment.

Fortunately, I committed the bypass function today.

If you do not change the resolution, the video codec can bypass and only audio can be transcode to Opus.

Below is a sample encode configuration.
<Encode> <Name>video_bypass_audio_opus</Name> <Video> <Bypass>true</Bypass> </Video> <Audio> <Codec>opus</Codec> <Bitrate>64000</Bitrate> <Samplerate>48000</Samplerate> <Channel>2</Channel> <Bypass>false</Bypass> </Audio> </Encode>
Try the latest dev branch.

One important thing is that required encoder(Such as OBS) setting.

1) H264.KeyInterval = 1~2 (recommend)
2) H264.BFrames = 0 (must)

If you have any more questions, feel free to contact us.

Thank you.

[duiniuluantanqin]

Hello, @cjagadis

Transcoding requires a lot of CPU performance. So, It's expensive in a GCP environment.

Fortunately, I committed the bypass function today.

If you do not change the resolution, the video codec can bypass and only audio can be transcode to Opus.

Below is a sample encode configuration.
<Encode> <Name>video_bypass_audio_opus</Name> <Video> <Bypass>true</Bypass> </Video> <Audio> <Codec>opus</Codec> <Bitrate>64000</Bitrate> <Samplerate>48000</Samplerate> <Channel>2</Channel> <Bypass>false</Bypass> </Audio> </Encode>
Try the latest dev branch.

One important thing is that required encoder(Such as OBS) setting.

1) H264.KeyInterval = 1~2 (recommend) 2) H264.BFrames = 0 (must)

If you have any more questions, feel free to contact us.

Thank you.

hello, i have the same question, and i use it in docker.i need to confirm that bypass is supported in docker or not.
Thank you.

[getroot]

It also works with Docker.
You can find the image at airensoft / ovenmediaengine: latest on DockerHub. It is installed by default in / opt / ovenmediaengine / bin.

[cjagadis]

Thanks Jeheon. We will test it soon. Best Regards, Jagadish Channagiri Jagadish Moogilu <http://www.moogilu.com> jagadish@moogilu.com +1 408 884 0325 (O) +1 650 245 1884 (C)

…

On Tue, Mar 3, 2020 at 3:12 AM Jeheon Han ***@***.***> wrote: It also works with Docker. You can find the image at airensoft / ovenmediaengine: latest on DockerHub. It is installed by default in / opt / ovenmediaengine / bin. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#74?email_source=notifications&email_token=AADHQDD5KCYZBJQGLUZUIXDRFTQ27A5CNFSM4KXSFTJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENTCZFI#issuecomment-593898645>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADHQDC7TQRVRXUD4AL5SALRFTQ27ANCNFSM4KXSFTJQ> .

[cjagadis]

Thanks. Yes, this is exactly what we are looking for. We will transcode the Audio and send H264 baseline and will also have H264Bframes=0 in our H264 encoding. I do appreciate your help. Best Regards, Jagadish Channagiri Jagadish Moogilu <http://www.moogilu.com> jagadish@moogilu.com +1 408 884 0325 (O) +1 650 245 1884 (C)

…

On Tue, Mar 3, 2020 at 1:06 AM duiniuluantanqin ***@***.***> wrote: Hello, @cjagadis <https://github.com/cjagadis> Transcoding requires a lot of CPU performance. So, It's expensive in a GCP environment. Fortunately, I committed the bypass function today. If you do not change the resolution, the video codec can bypass and only audio can be transcode to Opus. Below is a sample encode configuration. <Encode> <Name>video_bypass_audio_opus</Name> <Video> <Bypass>true</Bypass> </Video> <Audio> <Codec>opus</Codec> <Bitrate>64000</Bitrate> <Samplerate>48000</Samplerate> <Channel>2</Channel> <Bypass>false</Bypass> </Audio> </Encode> Try the latest dev branch. One important thing is that required encoder(Such as OBS) setting. *1) H264.KeyInterval = 1~2 (recommend) 2) H264.BFrames = 0 (must)* If you have any more questions, feel free to contact us. Thank you. hello, i have the same question, and i use it in docker.i need to confirm that bypass is supported in docker or not. Thank you. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#74?email_source=notifications&email_token=AADHQDCHSP5JBARESSHKMWLRFTCBPA5CNFSM4KXSFTJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENSVCLI#issuecomment-593842477>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADHQDHYT3A424FN6KSUPGLRFTCBPANCNFSM4KXSFTJQ> .

[getroot]

Thank you!

[duiniuluantanqin]

It also works with Docker.
You can find the image at airensoft / ovenmediaengine: latest on DockerHub. It is installed by default in / opt / ovenmediaengine / bin.

hello，
i had test the Bypass with docker. CPU usage dropped from 150% to 30%. But, the video clip, and the audio is normal.

[getroot]

@duiniuluantanqin
Thanks for sharing your experience.

[duiniuluantanqin]

@duiniuluantanqin
Thanks for sharing your experience.

How can I solve this problem?
I do appreciate your help in advance.

[getroot]

Sorry, I didn't understand your problem.
You said "Video clip and the audio is normal." and CPU usage dropped from 150% to 30%.
What is the problem? Please upload your Server.xml with the problem.

[getroot]

This issue has been closed since it has been inactive for quite some time. If you want to continue discussing this issue, please feel free to reopen it.