ShellMonkey

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

It’s not so much a question of one vs another. It was asked the most cost effective way to accomplish such.

Last I knew Plex required an ongoing subscription for some aspects that Jelly has for free, so that consideration is part of cost effectiveness.

Personally I have Emby simply out of inertia since I bought a lifetime licence before there was a Jellyfin spun off, but didn’t propose that because it would be an unneeded cost.

It’s basically a web server to play media on the front end and a metadata manager and conversion engine on the back.

Pretty well the same as Plex but there’s less reliance on external services, more truly self contained and less subscription. There are client apps for most streaming boxes that I know of.

https://support.plex.tv/articles/202526943-plex-free-vs-paid/

Avoiding Plex for something like Jellyfin is a start.

Past that, it doesn’t take a lot to run such a service unless it needs transcoding which is where it gets dicey for realtime streaming.

If you have a standard expected output you might get away with bulk stranscoding ahead of time and then run things on some little nuc or an old laptop.

More public for AI training as well then

If I recall right off hand it’s 92 cores, 64+8+8+12 between them. Been looking to merge a couple of the smaller ones into the others but it’s not a small task.

Way too damn much, around 700w between 4 rack servers and associated gear

Mostly Zabbix and my own email server. Way I figure if there’s something broken enough to take out the email internally I’m probably already dealing with a broader issue.

I use a different ‘type 1’ hypervisor, create a small handful of VMs and then have a mess of containers inside containers in a couple of those. There’s a distinct VM for email since that has so many special requirements that it was just easier, one lxc/incus container host for admin tools, one for user apps, one for piefed because all these fediverse apps are so busy with the constant exchanges it kind of needs its own host to not affect others…

Why is more a case of ease of administration frankly. Pretty much everything gets auto patched and backed up and it’s easy to put up a new service or restore things if I hose something up.

The structure though has been a years long evolution that started out as ‘I just want a NAS to share files’ which then needed a frontend to make it more user friendly, and another app to play videos, and why not organize different file types rather than just dump em in a folder…

Image

Nope

Borg is it’s own thing, just handy to have it built in and preconfigured to work. If you run VMs on your working host instead of directly on the machine you could just back those up for pretty much the same effect, though it wouldn’t usually be a realtime backup.

The next cloud data is fine being remote, when I say realtime I guess it could be better said as time sensitive. A database needs to update something and read it back in the right sequence for it to work properly. Just retrieving a file doesn’t have those issues.

If you happened to use it in a way like shared collaboration of a document with realtime updates it might be an issue, but I expect in that case the revisions would hit the DB first and then be put to the file as a secondary operation. Never tried that myself though.

Without getting into things like a SAN it’s generally not a good plan to put anything that needs realtime access remote to the device processing it. DBs are constantly making updates and introducing the odd bit of latency or a disconnect can make for lots of issues. I also have a worker/storage split setup and for a while tried just running the VMs as a whole using remote storage to host the vdisk, it wasn’t pretty even with a separate network dedicated to it.

For NC particularly, if you use their official AIO docker setup there is a built in borg backup you can store remotely and it makes restoration pretty painless.

You can buy whole kits to build your own, the capacity to control what is made with the is about as much as if you tried to ban someone with a table saw from building a birdhouse.

My go to for messing with chat bots is Kobold that’ll let you split the work between multiple GPUs. I get the impression the actual processing is only done on one but it lets you load larger models with the extra memory.

I was using a Nvidia 3060 for a while, then had 2 in one box, then switched to a 3090.

The amount of vram is a big factor for decent performance. Getting it to not sound like a predictably repetitive bot though is a whole separate thing that is still kind of elusive.

I was probably using Emby already by then, had bought a lifetime license since it didn't require bouncing things off and outside server like Plex did (or was it that Plex was a renewing subscription, I forget) , so it just stayed out of inertia.

I can't say I've given Jellyfin a proper try (as in using it and the clients exclusively for a long period) but we have been using Emby for quite a while before I knew it existed.

If I'm not mistaken Jellyfin is actually a fork of Emby so they're pretty similar, but one is a bit older.