overview for webnet

Plex/Jellyfin Transcode Performance on x86 MiniPCs or a ZimaBoard in c/selfhosted

[–] webnet 1 points 8 months ago (1 children)

I've honestly been considered going the other way. I have a bunch of h.264 files that I'd like to convert to h.265. I recently heard about Tdarr, and am considering that for a future weekend project to reclaim storage space.

I think directing my friends that can to move to players that don't suck would help with the transcoding bottleneck. But some of the other responses make me feel like I'm overly concerned about it.

17

Plex/Jellyfin Transcode Performance on x86 MiniPCs or a ZimaBoard (self.selfhosted)

submitted 8 months ago by webnet to c/selfhosted

8 comments fedilink

I recently got a crazy deal on an 832 ZimaBoard and I'm hoping to use it to replace my beefy old gaming pc as my media server setup. I aim to achieve 7 concurrent 1080p streams and at least 4 1080p transcodes on either Plex or Jellyfin.

If you have a MiniPC or a Zimaboard, what's your maximum number of concurrent streams and transcodes you've achieved on Plex or Jellyfin?
How did the performance fare, especially at peak usage?
Any special configurations or hardware tweaks you'd recommend for optimal performance?
Do you recommend any low power, small form factor alternatives?

Thanks for reading!

How to specify port number in compose file that is behind vpn container in c/selfhosted

[–] webnet 6 points 8 months ago (1 children)

qBittorrent has an option to define the WEBUI_PORT. If you want to access it on say, port 8585, set this environment variable to WEBUI_PORT=8585. Then in gluetun, continue to reference it as you do above. Hope this helps. https://registry.hub.docker.com/r/linuxserver/qbittorrent

  qbittorrent:  
    container_name: qbittorrent  
    image: linuxserver/qbittorrent:latest
    environment:
      - WEBUI_PORT=8585
    restart: unless-stopped
    network_mode: container:vpn  
    volumes:  
     - /docker/appdata/qbitorrent:/config