Current setup is PMS running on a Synology 5-bay, and another PMS running on a Shield Pro. The NAS server is primarily used for remote streaming, while the Shield serves to my home LAN (AppleTVs mainly).
I’ve been seeing stuttering on larger files, either using the Plex app or Infuse, and I’m fairly certain the Synology is the weak link. Network performance in the house has pretty solid, though admittedly I could stand to test it more thoroughly. I’ve been looking at moving my library to a standalone system. I’ve been looking at the Beelink ME Mini (which happens to be on sale!). What I don’t know is the best way to build this out.
I don’t want to have to buy all 6 SSDs (ar at least 6x4TB ones!) at once, so I’d be looking at either a stock Linux (Ubuntu or Rocky) install w/ I guess a BTRFS pool for the SSDs (I’m guessing I can use the eMMC for OS depending on how big the install is - that or use the SSD in slot 4). Alternatively, i could possibly set up TruNAS w/ the Plex pp to manage the storage.
As for populating the media, I plan to keep the Synology as the central repo of my data. I have it replicating to another NAS at my dad’s house, with movies/music/tv replicating using Syncthing. I plan to also use Syncthing to populate the Beelink.
Anyway, please poke holes in this plan and/or suggest a better one. My main goals are to get the media I’m streaming off spinning disk w/ minimal power draw (didn’t mention that above) in a way that I can expand storage as necessary to accommodate the media library. Nothing’s purchased yet, so I’m not married to the hardware. I would ideally like to convert the library to h.265 or even AV1 if I can make it work.
ETA: For clarity: I’m not transcoding AFAIK. My Shield mounts the Synology over SMB and mostly works fine, until I try to play anything 4k - then I get stuttering. On the surface, this sounded like a network issue, but I can’t find a problem w/ the LAN. My thought was to move the PMS to a single location w/ local storage, and use the Synology just as an archive.
ETA2: FWIW, I have not expanded the memory on the Synology or installed any cache drives.
just get a cheap n100 box, don’t overspend
Which part is your problem, serving the media from disk, or transcoding and serving that stream?
I’ve updated the OP to answer this. I think serving the media from the spinning disk is the heart of the problem.
Prove it with data, else you’ll just be blindly throwing money down the drain.
I just did something sort of like what you are doing and after a few hiccups, it’s working great. My Synology just couldn’t handle transcoding with docker containers running in the background.
Couple differences from your plan: I chose a N100 over the N150 because it used less power and I wasn’t loading up CPU dependent tasks on the thing. The N150 is about 30% faster if memory serves, but draws more power. Second, do you really need a second m.2 SSD BTRFS volume? Your Synology is perfectly capable of being the file storage. I’d personally spend the money you’d save buying a smaller N150 device on a tasty drive to expand the existing capacity then start a second pool from scratch.
Finally, I wouldn’t worry about converting media unless you are seriously pinched for space. Every time you do, you lose quality.
If you went from “everything works”, to “now it stutters”, then you either have a networking issue, or a resource issue on the source.
Did you update something recently?
Do you have network stats from your router?
Do some devices work fine, and others don’t?
I see no other issues from the network. The thing that “changed” is me trying to watch 4k stuff on my plex server. Up until recently, I didn’t bother with 4k. No real reason for trying it now, TBH. I’ve never felt that 4k was necessary for home viewing on anything smaller than a 100” screen (my largest if 75”).
Okay, so what’s your network look like?
Specs on your router, is this wired or wireless to the Shield, how much other traffic are the other network clients pulling, and is this a constant, or just happens intermittently?
Everything’s wired. Router is a TP-Link BE63, 2 APs w/ wired backhaul. Shield is on the same switch as the synology. STBs are throughout the house, but generally max 3-hops to the Shield/Synology. All Netgear bluebox 1Gb dumbswitches. At some point in the near future, I plan on getting this stuff to a central switch, so everything is a leaf switch away from it.
ETA: if I’m watching something, the network is generally pretty quiet. I have most data-intensive things (downloads, backups, off-site replications) set to happen in the wee-hours.
Netgear is…kinda shit. Is that 1Gb for the whole switch, or per-port? Any traffic steering on the network?
I would double and triple check your not transcoding. Even if you’re watching on the client at whatever the files native resolution is depending on the codec of the file you might still be transcoding. For instance with 1080p anything h265 or AV1 is transcoded into h264 by the server. There’s also a few other situations where Plex with force transcoding or down convert the video whether you want it to or not.
Your NAS shouldn’t be having trouble serving the file to Plex I’d bet it’s transcoding in the background and you just don’t realize it.
I would ideally like to convert the library to h.265 or even AV1 if I can make it work.
Unless you’ve downloaded remuxes (which I doubt), I’d seriously recommend redownloading instead of converting your existing files.
h.265 and especially AV1 take a long time to encode by CPU, and hardware encoding won’t give you any space savings, unless you’re okay with losing much details.
Redownloading is most definitely faster, will result in more space savings for the quality you’ll get. PS: Unless you’ve got data volume limits, but even then I’d recommend slowly upgrading over time. It’s quite simple with TRaSH guides and giving h.265 a higher score.
I believe I have a very similar issue as you. It only occurs on remux/high bitrate 4k videos. Happens no matter the player etc. I currently fix this issue by putting on that limit qbit upload speed and everything plays fine then.
I am interested in what your solution is.
limit qbit upload speed
Not sure what you’re referring to here.
Its a qbittorrent setting. you can set upload and download limits to turn on at specific times or when you want to by clicking the little speed dial.
So if you are not utilizing those harddrives for other uses such as torrents thn disregard.
Got it: qbit == qbittorrent. I’ve thought about getting the remaining docker containers off of the Synology. I may look into that this weekend.
Yea I would test a large file and as soon as it buffers put a limit on quittorrent or something that could be reading and writing lots of data from those drives and see if that fixes the issue. I wish there was a better way.
TBH I would consider an M4 Mac Mini and either a NAS or DAS to go along with it. The power, efficiency, and price make it a really compelling choice.
I did this. It is a mixed bag.
