A refurbished thin client from eBay. Or a refubed sff/usff.
They are pretty much the same price these days, and come with a case/PSU.
If you don’t need the GPIO and special connectors that a raspberry pi has, sff/usff is going to be cheaper, has upgradeable ram&sata and some have pcie3.0 slot.
Running pihole (let’s be honest, a huge reason people buy a pi)? Get a usff/sff, slap an SSD (probably the cost of a raspberry pi case/PSU/SD-card) in there and an intel i340-t4 4port NIC (this is extra. Can just use the onboard NIC), and install proxmox. Then run pihole in a VM. And now you have spare capacity to run a whole bunch of other fun things, with the safety net of snapshots and backups so if you mess up a config you can just roll another VM.
5? Holy heck, that’s amazing. I remember helping people that had built streaming rigs to use during the pandemic, and wondering why their production was stuttering and having issues with a bunch remote callers. Some of that work ended up being CPU bound.
Although, looks like that patch is for Linux? Not much use if your running vmix or some other windows-only software.
In OPs case, however, that’s not a problem
If you are doing high bandwidth GPU work, then PCIe lanes of consumer CPUs are going to be the bottleneck, as they generally only support 16 lanes.
Then there are the threadrippers, xeons and all the server/professional class CPUs that will do 40+ lanes of PCIe.
A lane of PCIe3.0 is about 1GBps (Byte not bit).
So, if you know your workload and bandwidth requirements, then you can work from that.
If you don’t need full 16 lanes per GPU, then a motherboard that supports bifurcation will allow you to run 4 GPUs with 4 lanes each from a CPU that has 16 lanes if PCIe. That’s 4GBps per GPU, or 32Gbps.
If it’s just for transcoding, and you are running into limitations of consumer GPUs (which I think are limited to 3 simultaneous streams), you could get a pro/server GPU like the Nvidia quadros, which have a certain amount of resources but are unlimited in the number of streams it can process (so, it might be able to do 300 FPS of 1080p. If your content is 1080p 30fps, that’s 10 streams). From that, you can work out bandwidth requirements, and see if you need more than 4 lanes per GPU.
I’m not sure what’s required for AI. I feel like it is similar to crypto mining, massive compute but relatively small amounts of data.
Ultimately, if you think your workload can consume more than 4 lanes per GPU, then you have to think about where that data is coming from. If it’s coming from disk, then you are going to need raid0 NVMe storage which will take up additional PCIe lanes.
These guys do short depth PCs. I wish I knew where they got their cases from, because they are really nice!
But I haven’t found anything decent in the wild (I eventually gave up and got a deeper rack so I can use old r730 servers)
It was PHP and Laravel.
I started doing fancier things with websockets, redis, cronjobs etc.
Anything “designed for” laravel hosting wasn’t cheap. So, I learned how to get a VM going and set it up for webhosting.
Windows is still my daily driver due to Office, Visual Studio and gaming.
But I have a bunch of VMs and servers, and they are all Debian.
I enjoy Linux, but I haven’t gone whole-hog into a desktop environment or whatever. Everything has been CLI based
Yeh, it’s obviously a nonsense argument.
Linus even suggested 2 backronyms for it, none of which have the j sound.
And there is precedence for git being pronounced git not jit.
Women Vs world? Women Vs Woo? Women Vs work? Women Vs wonder?
Cause the “wom” sequence would be…
Women Vs Womb?
Women Vs Wombat?
The arguement is obviously nonsense.
It’s going into syntax of words to get pronunciation, instead the acronym/name.
Which is funny, because that’s exactly what’s happening in the gif/jif argument.
Great.
However none of those have the g-i-f sequence and have the j sound.
They do have g-i-t sequences. So it suggests that the f makes the g pronounced like a g not a j.
Intact, you could use examples like “digit” to argue the versioning software should be pronounced jit.