this post was submitted on 21 Oct 2024
121 points (100.0% liked)

chapotraphouse

13484 readers
956 users here now

Banned? DM Wmill to appeal.

No anti-nautilism posts. See: Eco-fascism Primer

Vaush posts go in the_dunk_tank

Dunk posts in general go in the_dunk_tank, not here

Don't post low-hanging fruit here after it gets removed from the_dunk_tank

founded 3 years ago
MODERATORS
 

blob-on-fire

TankieTube is suffering from success.

you are viewing a single comment's thread
view the rest of the comments
[–] JoeByeThen@hexbear.net 22 points 7 hours ago (1 children)

Is this because of all the remote transcoding, or are you getting that much traffic?

[–] TankieTanuki@hexbear.net 24 points 7 hours ago* (last edited 7 hours ago)

Both.

When you enable "remote runners" in the PeerTube settings, the server stops transcoding entirely. In order to continue using the server CPU, it's necessary to register the local machine as a "remote" runner.

I did that last week. Now all the transcoding is run as a separate process by a dedicated Linux user, prunner. However, when I first registered the local runner, I said "send all the finished files to https://tankie.tube" because that's what the docs said. That had the effect of doubling all the transcoding traffic to the server because it was sending files to itself via the public net. Very bad. so I changed it to http://127.0.0.1:9000.

Now there is no more doubling of the traffic, but it's apparently still too much traffic. If I were to add any truly "remote" runners, it would increase the traffic even more.