Selfhosted

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

kind of.. a "AMD GX-420GI SOC: quad-core APU" the one with no L3 Cache, in an Thin Client and 8Gb Ram. old Laptop ssd for Storage (128GB) Nextcloud is usable but not fast.

edit: the Best thing: its 100% Fanless

All my stuff is running on a 6-year-old Synology D918+ that has a Celeron J3455 (4-core 1.5 GHz) but upgraded to 16 GB RAM.

Funny enough my router is far more powerful, it's a Core i3-8100T, but I was picking out of the ThinkCentre Tiny options and was paranoid about the performance needed on a 10 Gbit internet connection

I faced that only with different editions of Windows limiting it by itself.

The oldest hardware I'm still using is an Intel Core i5-6500 with 48GB of RAM running our Palworld server. I have an upgrade in the pipeline to help with the lag, because the CPU is constantly stressed, but it still will run game servers.

I'm hosting a minio cluster on my brother-in-law's old gaming computer he spent $5k on in 2012 and 3 five year old mini-pcs with 1tb external drives plugged into them. Works fine.

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.

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.

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.

Oldest I got is limited to 16GB (excluding rPis). My main desktop is limited to 32GB which is annoying, because I sometimes need more. But, I have a home server with 128GB of RAM that I can use when it's not doing other stuff. I once needed more than 128GB of RAM (to run optimizations on a large ONNX model, iirc), so had to spin up an EC2 instance with 512GB of RAM.

My first @home server was an old defective iMac G3 but it did the job (and then died for good) A while back, I got a RP3 and then a small thin client with some small AMD CPU. They (barely) got the job done.

I replaced them with an HP EliteDesk G2 micro with a i5-6500T. I don't know what to do with the extra power.

Wow, it's been a long time since I had hardware that awful.

My old NAS was a Phenom II x4 from 2009, and I only retired it a year and a half ago when I upgraded my PC. But I put 8GB RAM into that since it was a 64-bit processor (could've put up to 32GB I think, since it had 4 DDR3 slots). My NAS currently runs a Ryzen 1700, but I still have that old Phenom in the closet in case that Ryzen dies, but I prefer the newer HW because it's lower power.

That said, I once built a web server on an Arduino which also supported websockets (max 4 connections). That was more of a POC than anything though.

I used to self host some stuff on an old 2011 iMac. Worked fine, actually

Plex server is running on my old Threadripper 1950X. Thing has been a champ. Due to rebuild it since I've got newer hardware to cycle into it but been dragging my heels on it. Not looking forward to it.

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.

I'm still interested in Self-Hosting but I actually tried getting into self-hosting a year or so ago. I bought a s***** desktop computer from Walmart, and installed window server 2020 on it to try to practice on that.

Thought I could use it to put some bullet points on my resume, and maybe get into self hosting later with next cloud. I ended up not fully following through because I felt like I needed to first buy new editions of the server administration and network infrastructure textbooks I had learned from a decade prior, before I could continue with giving it an FQDN, setting it up as a primary DNS Server, or pointing it at one, and etc.

So it was only accessible on my LAN, because I was afraid of making it a remotely accessible server unless I knew I had good firewall rules, and had set up the primary DNS server correctly, and ultimately just never finished setting it up. The most ever accomplished was getting it working as a file server for personal storage, and creating local accounts with usernames and passwords for both myself and my mom, whom I was living with at the time. It could authenticate remote access through our local Wi-Fi, but I never got further.