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.

Sign up for GitHub

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

Jump to bottom

Using Chrome for Testing with GPU in Docker container is slower than chrome-headless-shell #4955

Open

samohovets opened this issue Feb 28, 2025 · 0 comments

Labels

bug

Member

samohovets commented Feb 28, 2025

Bug Report 🐛

I was testing rendering a React Three Fiber + Remotion composition with chromeMode: 'chrome-for-testing'.

Setup:

Docker container with CUDA pre-mounted (https://fly.io/docs/gpus/gpu-quickstart/)
Fly.io + NVIDIA L40S GPU
16 performance cores, 32GB RAM

When using Chrome for Testing, the render was slower X times than chrome-headless-shell, where X – concurrency.

Example:

Render time with concurrency 3 with Chrome Headless Shell: 7.10 minutes.
Render time with concurrency 3 with Chrome for Testing: 21.5 minutes.

So maybe there's an issue with parallelization since it's a single browser with multiple tabs?

I can provide an isolated reproduction. I'm creating this issue in case anyone else also encounters this.

The text was updated successfully, but these errors were encountered:

samohovets added the bug label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment