Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recommend a workflow for using the GPU on a AWS instance #2889

Closed
JonnyBurger opened this issue Sep 13, 2023 · 8 comments
Closed

Recommend a workflow for using the GPU on a AWS instance #2889

JonnyBurger opened this issue Sep 13, 2023 · 8 comments
Assignees

Comments

@JonnyBurger
Copy link
Member

Remotion 4.0 does not support Glibc 2.33 anymore, but there are no templates on AWS that have GPU drivers installed but use a new enough version of Glibc

@JonnyBurger JonnyBurger self-assigned this Sep 24, 2023
@bilalmughal
Copy link
Contributor

While working on GPU acceleration for headless Chrome/Chromium, I couldn't help but wonder: why not harness the full power of GPUs for video transcoding as well? I have just finished with my cost-centric analysis comparing CPU vs GPU for video transcoding and the results were astonishing, benchmark data reveal GPUs proved to be both faster and more cost-effective. You can check out my detailed findings here. So this compelled me even more to pitch this idea to the Remotion community.
This will not only offload more rendering workload to GPU but it will also free up the CPU, to perform so many general purpose tasks we generally need to perform.

And the best part is it's within our reach. All it takes is recompiling the FFmpeg binary with hardware acceleration support. I'm more than eager to lend a hand in this and see the results for myself.
Here is a graph from the post reflecting the stark difference in performance.
Transcoding-time-benchmark
https://mirzabilal.com/cpu-vs-gpu-for-video-transcoding-challenging-the-cost-speed-myth

@UmungoBungo
Copy link
Contributor

nice work! We have found that arm has better price performance than x86-based CPUs, which your post shows as well. I think it would be good to mention the architecture of each instance as I had to jump back and forth between your post and the AWS docs to understand 😄

@UmungoBungo
Copy link
Contributor

so based on the method in your post, you are suggesting that the Remotion renderer would first check if a GPU is available, and if it is, perform transcoding using the GPU?

@UmungoBungo
Copy link
Contributor

Related: #3013

@bilalmughal
Copy link
Contributor

bilalmughal commented Oct 16, 2023

@UmungoBungo Thank you, and the reason behind not mentioning the architecture as AWS has now finally standardized the naming convention, for example, any instance name with g is AWS Graviton, like G5g.xlarge and C7g.4xlarge, similarly i is for Intel. As in C7i.2xlarge and a is for AMD like C7a.xlarge

nice work! We have found that arm has better price performance than x86-based CPUs, which your post shows as well. I think it would be good to mention the architecture of each instance as I had to jump back and forth between your post and the AWS docs to understand 😄

@UmungoBungo
Copy link
Contributor

ahh I see, thanks for pointing that out! I had guessed g for Graviton and i for Intel but wasn't sure about the a

@bilalmughal
Copy link
Contributor

Related to #3038

@JonnyBurger
Copy link
Member Author

True, this is done now! https://www.remotion.dev/docs/miscellaneous/cloud-gpu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants