-
After installation, and setting a new password for admin. I uploaded a small home video as a user. it immediately failed when trying to transcode, apparently because the default memory setting is to low.
-
G girish moved this topic from Discuss on
-
Yep I bumped it from 256Mb (from memory) to 8Gb, it uploaded and transcoded the first 2 video files fine, the next 2 have just sat at transcoding for quite a few hours, and also the file I first uploaded that caused it to hit the limit and crash... unless I change the file name I get an "unknown error".
-
Yep I bumped it from 256Mb (from memory) to 8Gb, it uploaded and transcoded the first 2 video files fine, the next 2 have just sat at transcoding for quite a few hours, and also the file I first uploaded that caused it to hit the limit and crash... unless I change the file name I get an "unknown error".
@AartJansen sounds like a good thing to grab the logs for and see about the upstream devs making improvements.
-
hmm, yeah at 100% CPU for 4 hours transcoding one video... I doubt it can be improved so much as to make me want to have this impacting on the other important things that I want to run well.
@AartJansen yeah you have to know what you're getting into..
You could have a different upload process that perhaps offloads all the transcoding you want to a large free provider before saying thank you and uploading to your instance already transcoded?
-
I remembered the server has a nvidia 8400 GPU, and also found thats its driver was the generic nouveau, so have installed the correct nvidia driver instead hoping the ffmpeg process will automagically (peertube forums suggest it might) use GPU encoding, and perhaps molest the CPU less. It's worth noting the 4 hour encoding was for a 3.5 hour video, so perhaps its not going to be as problematic as I first thought. (I didn't realise it was that long beforehand, so a good test any way)
-
@AartJansen Good idea, I will bump the default memory limit.
