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
Comments
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. 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. |
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 😄 |
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? |
Related: #3013 |
@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
|
ahh I see, thanks for pointing that out! I had guessed |
Related to #3038 |
True, this is done now! https://www.remotion.dev/docs/miscellaneous/cloud-gpu |
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
The text was updated successfully, but these errors were encountered: