-
Notifications
You must be signed in to change notification settings - Fork 35
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
Distributed single-file transcoding #262
Comments
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
Would it be worthwhile to configure the excempt-issue-labels here: The label could then be applied to this issue to prevent it auto-closing. (I would also not be offended if you allow the issue to close as wont-do. I am not in terrible need of this feature, so please don't feel the need to keep it open for my sake 😊) |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for 14 days since being marked as stale. |
if i'm not mistaken the env setting STREAM_SPLITTING still exist? Does this setting not work or is it verry unstable? |
so i tried to implement and it somewhat works but maybe @pabloromeo you could point me to the right direction. So from what i can tell it is able to send tasks to different servers but the last send tasks just keeps on server3? My fork is here: https://github.com/FelixClements/clusterplex
|
Hi! If I remember correctly the idea had a bit more merit in processes like Optimizing a movie, which could be done in parallel in segments and then stitched back together. Also it's been years, so maybe somebody has already created something opensource which does part of that we could leverage or use as a dependency. Haven't has a time to look into it. One thing I never go to exploring was maybe splitting the audio transcoding from the video one, to be able to do them on separate nodes. |
Hey! Thank you so much for your detailed response! Your insights actually pointed me in the direction of hardware transcoding instead of stream splitting, which was immensely helpful. I went ahead and looked into hardware transcoding solutions and finally got it working, though it was quite challenging to implement within Docker Swarm. I ended up spending quite some time configuring the right setup and managing resource constraints specific to hardware acceleration. I'm really curious about your setup. How did you manage to get hardware transcoding working in your environment? Any tips or advice you could share would be greatly appreciated! to get it to work i had to
|
Yeah, hardware transcoding and Docker Swarm is quite a bit more challenging. |
Thanks for bringing up the topic of hardware transcoding with Docker Swarm and your experience with Kubernetes. I actually faced some similar challenges with hardware transcoding as well. In my specific use case, I made some file changes in my fork of the project to prioritise Intel support. If you're interested, feel free to check out my fork, where I’ve implemented these updates. You could maybe reference these changes or adapt them for your setup to possibly make the process easier for others wanting to get Intel hardware transcoding up and running in their environment. Let me know if you need further details or clarification, I’d be happy to help! Cheers |
Hi Felix. Can you give a bit more information as to which files to drop in the Drivers and Cache folders that you're mapping? |
Is your feature request related to a problem? Please describe.
It's possible that the individual nodes in the cluster may not be powerful enough to transcode 4K video in real time. Maybe a single node can only transcode 5 seconds of "video time" in 10 seconds of "real time", not enough to keep up with continuous playback.
Describe the solution you'd like
Would be great if a single transcode job could be "chunked" and distributed amongst the cluster. For example, the video could be split into 5-second chunks, each sent to a node to transcode and then recombined by the orchestrator. In the example above, three nodes working together would be able to transcode 15 seconds of "video time" in 10 seconds of "real time", which is sufficient to enable continuous playback.
The text was updated successfully, but these errors were encountered: