I am looking to basically just transition to a small time, forever on, server to support my growing Plex footprint. I don’t need anything top of the line, and I’ve already crimped my lines to the room.

What’s the most cost effective way to go about this? Figured i would come to the pros.

Thanks!

  • German The Jackal@pawb.social
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    2
    ·
    1 day ago

    Considering they’re asking for cost effective ways, and Jellyfin has notoriously poor resource management especially in the memory department, no.

    • ShellMonkey@piefed.socdojo.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 day ago

      Might have to spin up a JF instance to check, right now I’m using Emby that JF was forked from some while ago and don’t see anything horrid. About 1GB memory for one that’s been up and running for a good while.

      image

      • German The Jackal@pawb.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        10 hours ago

        1GB is egregious for what amounts to a file server that can spawn ffmpeg. Plex uses like 10x less. Last time I tried Jellyfin it ate 9GB and nuked my NAS out of existence, purely because it tried to scan my fairly modest library.

        C# on .NET is pretty horrible on resources and efficiency for stuff like this - this also sometimes happens to a lot of the more established *arr software

        Here’s Plex currently generating some audio loudness data on an entire season in the background. In a container (it’d be even leaner if it ran bare metal). I’ve never seen it even reach 500MB under the worst circumstances imaginable.