misskey has a hard time displaying videos too
I think it's because misskey wants to transcode video instead of playing it directly
I think it's because misskey wants to transcode video instead of playing it directly
@Jessica unless something changed Misskey doesn't transcode any videos. The most it does is use ffmpeg to generate a thumbnail for the video.
@graf @Jessica oh yeah I've taken GLC down a few times because I went on a webm posting spree and that caused well over 50 transcoding jobs to all be running at once.
Iirc mastodon is nice enough to run the transcoding jobs with a nice value of 19 so it really shouldn't interfere with anything but when you're trying to transcode 50 HD videos at once that's a lot of RAM...
I'm pretty sure all the transcoding jobs filled up the RAM and caused @matrix's server to lock up.
Now, iirc if it can't transcode the video in like 3 minutes it gives up and just cancels the transcoding job but when you're SJW you can easily post well over 100 webms in that timeframe.
It wouldn't surprise me if mastodon uses /tmp to store the webms until they're transcoded (or at least copies them there before working on them. Probably even writes the transcoded output there before copying it back too) which would eat through yet even more RAM.
No support for hardware transcoding either.
Iirc mastodon is nice enough to run the transcoding jobs with a nice value of 19 so it really shouldn't interfere with anything but when you're trying to transcode 50 HD videos at once that's a lot of RAM...
I'm pretty sure all the transcoding jobs filled up the RAM and caused @matrix's server to lock up.
Now, iirc if it can't transcode the video in like 3 minutes it gives up and just cancels the transcoding job but when you're SJW you can easily post well over 100 webms in that timeframe.
It wouldn't surprise me if mastodon uses /tmp to store the webms until they're transcoded (or at least copies them there before working on them. Probably even writes the transcoded output there before copying it back too) which would eat through yet even more RAM.
No support for hardware transcoding either.
Follow
@sjw @Jessica @graf That was when BuyVM still had the old Xeons.
Mastodon just uses ffmpeg and that doesn't store the whole video in RAM. All attachments are first placed into /tmp and processed there.
What filled up the RAM was the growing job queue because all the active job threads were waiting for the webms to process and when they finally did another webm was waiting in the queue.
