Replies: 3 comments
-
Fixed this now by increasing memory for the virtual machine, and in my youtube2mediacms checking when encoding is done for an upload before uploading a new video. |
Beta Was this translation helpful? Give feedback.
-
Hi, thanks for reporting. I remember in a number of cases that I've uploaded a big number of videos in a single server, in one case it would run ffmpeg and transcode for 2-3 weeks before completing all videos/profiles. The idea is that a single task runs per cpu core (a task can be ffmpeg on a single video for a single profile, or ffmpeg on a single chunk of a video for a single profilke), so that all cpus are occupied. I'm not sure sure what the condition could be that it ended in OOM, eg could it be running other programs as well? If this happens again, do check the number of ffmpeg tasks running (eg Thanks! |
Beta Was this translation helpful? Give feedback.
-
I will replicate the behaviour i've seen to see what is going on. Currently my youtube2mediacms seems to handle this perfectly by waiting on every encoding profile for an uploaded video to complete before uploading the next. So its not really an issue anymore (for me atleast) 😂 |
Beta Was this translation helpful? Give feedback.
-
I've been using mediacms locally with a virtual machine of 4 threads, 4gb ram, and an ssd of 100gb (According to These docs ). I'm basically the only one adding videos, and there are maybe a maximum of 5 people that watch 1-3 videos per day.
I see alot of OOM kills when i add alot of videos, which keeps the encoding processes in limbo in the admin interface.
Wondering if there is any way to keep the encoding from starting when the machine is using alot of performance for other encoding jobs. Maybe set a maximum number of threads for the ffmpeg encodes or something?
Would love to hear your thoughts.
Server specs
Logs
Beta Was this translation helpful? Give feedback.
All reactions