Selfhosted

Fuck ive been dealing with that + max RAM speed limitations for a month.

Testing federation from my shit hardware.. 😅

N...not quite...

Maybe a more reasonable question: Is there anyone here self-hosting on non-shit hardware? 😅

Does this count ARMv6 256MB RAM running OpenMediaVault...hmm I have to fix my clock. LOL

I run a local LLM on my gaming computer thats like a decade old now with an old 1070ti 8GB VRAM card. It does a good job running mistral small 22B at 3t/s which I think is pretty good. But any tech enthusiast into LLMs look at those numbers and probably wonder how I can stand such a slow token speed. I look at their multi card data center racks with 5x 4090s and wonder how the hell they can afford it.

7th gen intel, 96GB mismatched ram, 4 used 10TB HDD, one 12 with a broken sata connector that only works because it's sitting just right in a sled. A couple of 14's one M.2 and two sataSSD. It's running Unraid with 2 VM's (plex and Home Assistant), one of which has corrupted itself 3 times. A 1080 and a 2070.

I can get several streams off it at once, but not while it's running parity check and it can't handle 4k transcoding.

It's not horrible, but I couldn't do what I do now with less :)

I started my self hosting journey on a Dell all-in-one PC with 4 GB RAM, 500 GB hard drive, and Intel Pentium, running Proxmox, Nextcloud, and I think Home Assistant. I upgraded it eventually, now I'm on a build with Ryzen 3600, 32 GB RAM, 2 TB SSD, and 4x4 TB HDD

Not anymore. My main self-hosting server is an i7 5960x with 32GB of ECC RAM, RTX 4060, 1TB SATA SSD, and 6x6TB 7200RPM drives.

I did used to host some services on like a $5 or $10 a month VPS, and then eventually a $40 a month dedi, though.

My home server runs on an old desktop PC, bought at a discounter. But as we have bought several identical ones, we have both parts to upgrade them (RAM!) as well as organ donors for everything else.

I used to selfhost on a core 2 duo thinkpad R60i. It had a broken fan so I had to hide it into a storage room otherwise it would wake up people from sleep during the night making weird noises. It was pretty damn slow. Even opening proxmox UI in the remotely took time. KrISS feed worked pretty well tho.

I have since upgraded to... well, nothing. The fan is KO now and the laptop won't boot. It's a shame because not having access to radicale is making my life more difficult than it should be. I use CalDAV from disroot.org but it would be nice to share a calendar with my family too.

I moved from a Drll R710 with dual docket Xeons to a rack mount desktop case with a single Ryzen R5 5600G. I doubled the performance and halved the power consumption in one go. I do miss having idrac though. I need a KVM over IP solution but haven't stomached the cost yet. For how often I need it it's not an issue.

Look for a processor for the same socket that supports more RAM and make sure the Motherboard can handle it - maybe you're lucky and it's not a limit of that architecture.

If that won't work, breakup your self-hosting needs into multiple machines and add another second hand or cheap machine to the pile.

I've worked in designing computer systems to handle tons of data and requests and often the only reasonable solution is to break up the load and throw more machines at it (for example, when serving millions of requests on a website, just put a load balancer in front of it that assigns user sessions and associated requests to multiple machines, so the load balancer pretty much just routes request by user session whilst the heavy processing stuff is done by multiple machines in such a way the you can just expand the whole thing by adding more machines).

In a self-hosting scenario I suspect you'll have a lot of margin for expansion by splitting services into multiple hosts and using stuff like network shared drives in the background for shared data, before you have to fully upgrade a host machine because you hit that architecture's maximum memory.

Granted, if a single service whose load can't be broken down so that you can run it as a cluster, needs more memory than you can put in any of your machines, then you're stuck having to get a new machine, but even then by splitting services you can get a machine with a newer architecture that can handle more memory but is still cheap (such as a cheap mini-PC) and just move that memory-heavy service to it whilst leaving CPU intensive services in the old but more powerful machine.

The beauty of self hosting is most of it doesn't actually require that much compute power. Thus, it's a perfect use for hardware that is otherwise considered absolutely shit. That hardware would otherwise go in the trash. But use it to self host, and in most cases it's idle most of the time so it doesn't use much power anyway.

I just upgraded to a Xeon E5 v4 processor.

I think the max RAM on it is about 1.5 TiB per processor or something.

It's not new, but it's not that old either. Still cost me a pretty penny.

Running a bunch of services here on a i3 PC I built for my wife back in 2010. I've since upgraded the RAM to 16GB, added as many hard drives as there are SATA ports on the mobo, re-bedded the heatsink, etc.

It's pretty much always ran on Debian, but all services are on Docker these days so the base distro doesn't matter as much as it used to.

I'd like to get a good backup solution going for it so I can actually use it for important data, but realistically I'm probably just going to replace it with a NAS at some point.

It's not absolutely shit, it's a Thinkpad t440s with an i7 and 8gigs of RAM and a completely broken trackpad that I ordered to use as a PC when my desktop wasn't working in 2018. Started with a bare server OS then quickly realized the value of virtualization and deployed Proxmox on it in 2019. Have been using it as a modest little server ever since. But I realize it's now 10 years old. And it might be my server for another 5 years, or more if it can manage it.

In the host OS I tweaked some value to ensure the battery never charges over 80%. And while I don't know exactly how much electricity it consumes on idle, I believe it's not too much. Works great for what I want. The most significant issue is some error message that I can't remember the text of that would pop up, I think related to the NIC. I guess Linux and the NIC in this laptop have/had some kind of mutual misunderstanding.