Yeah it’s the drives and the controller for all the drives that are making the power usage what it is. I could replace some of the older drives with a newer one and be able to ditch the smaller drives and controllers, but it seems a waste to do that until they die.

Also, I wouldn’t mind ditching for a Sufficient™ amount of nvme storage, but SSDs aren’t actually getting cheaper and are probably going to do the opposite, so I’ll likely end up doing uh, nothing,

The flipside is: why the hell doesn’t any game work on eight gigabytes of VRAM? Devs. What are you doing? Does Epic not know how a texture atlas works?

It’s not that they don’t work.

Basically what you’ll see is kinda like a cache miss, except the stall time to go ‘oops, don’t have that’ and go out and get the required bits is very slow, and so you can see 8gb cards getting 20fps, and 16gb ones getting 40 or 60, simply because the path to get the missing textures is fucking slow.

And worse, you’ll get big framerate dips and the game will feel like absolute shit because you keep running into hitches loading textures.

It’s made worse in games where you can’t reasonably predict what texture you’ll get next (ex. Fortnite and other such online things that are you know, played by a lot of people) but even games where you might be able to reasonably guess, you’re still going to run into the simple fact that the textures from a modern game are simply higher quality and thus bigger than the ones you might have had 5 years ago and thus 8gb in 2019 and 8gb in 2025 is not an equivalent thing.

It’s crippling the performance of the GPU that may be able to perform substantially better, and for a relatively low BOM cost decrease. They’re trash, and should all end up in the trash.

Anecdata, but SSDs will last longer than you want to use them in terms of write endurance.

My NAS OS SSDs are 500gb hynix drives from about 8 years ago, and they’re pushing 150 TBW.

150TB is a LOT of write cycles on a small drive, and they’re still reporting 94% endurance remaining.

The controller will die or I’ll upgrade well before that breaks at the rate it’s going.

Also keep in mind that you can read flash all you want and that doesn’t wear anything (unlike a HDD, amusingly), so for most consumer use cases, they’ll load the drive up with their data, and then only slowly modify or add to it, but have lots and lots of read access.

HDDs will draw around 4W idle each, 8W in total

Whether your drives are idle is also a very use-case specific thing and I wouldn’t spend any time trying to generalize based on that math as a “oh this is how it works for everyone”.

In my case, I’ve got 5 drives all spun up at all times because of torrrent clients, Jellyfin users, and just general media acquisition and public content serving.

This thing would dramatically reduce my power footprint and save me giant buckets of money over it’s lifespan while being smaller/faster IO performance/lower noise.

(My current nas sucks down about 120-140w 24/7, so…)

Basically every one of them made in the past 4 or 5 years?

Some are better than others - CP2077, for example, will happily use all 16 threads on my 7700x, but something crusty like WoW only uses like, 4. Fortnite is. 3 or so, unless you’re doing shader compilation where it’ll use all of them, and so on - but it’s not 2002 anymore.

The issue is that most games won’t use nearly as many cores as Intel is stuffing on a die these days, which means for gaming having 32 threads via e-cores or whatever is utterly pointless, but having 8 cores and 16 threads of full-fat cores is very much useful.

And they also had the turn-into-a-zombie plague event when Wrath launched, too.

As I recall, that mostly just made everyone rage because the assholes running around spreading it everywhere were just annoying the crap out of everyone and the general thought is they just needed to fuck off and find something else to do.

Or, basically, Covid.

And more fun, lots of laptops have really goofy routing. I’ve got one where the DP alt mode on the USB-C ports are on the dGPU, but the HDMI ports are on the iGPU. And the internal panel is on the iGPU unless you switch it to be on the dGPU because yay mux.

Why? I don’t know. Too much meth while laying the board out or something I guess.

As with all things email, they probably really wanted to make sure that the mails were delivered and thus were using a commercial MTA to ensure that.

I’d wager, even at 20 or 30 or 40k a year, that’s way less than it’d cost to host infra and have at least two if not three engineers available 24/7 to maintain critical infra.

Looking at my mail, over the years I’ve gotten a couple hundred email from them around certificates and expirations (and other things), and if you assume there’s a couple million sites using these certs, I could easily see how you’d end up in a situation where this could scale in cost very very slowly, until it’s suddenly a major drain.

Very very little. It’s a billion tiny little bits of text, and if you have image caching enabled, then all those thumbnails.

My personal instance doesn’t cache images since I’m the only one using it (which means a cached image does nobody any good), and i use somewhere less than 20gb a month, though I don’t have entirely specific numbers, just before-lemmy and after-lemmy aggregates.

ArchiveBox is great.

I’m big into retro computing and general old electronics shit, and I archive everything I come across that’s useful.

I just assume anything and everything on some old dude’s blog about a 30 year old whatever is subject to vanishing at any moment, and if it was useful once, it’ll be useful again later probably so fuck it, make a copy of everything.

Not like storage is expensive, anyway.

Are uptimekuma and whatever you’re trying to monitor on the same physical hardware, or is it all different kit?

My first feeling is that you’ve got some DNS/routing configuration that’s causing issues if you’re leaving your local network and then going through two layers before coming back in, especially if you have split horizon DNS.

The big thing for #2 would be to seperate out what you actually need vs what people keep recommending.

General guidance is useful, but there’s a lot of ‘You need ZFS!’ and ‘You should use K8s!’ and ‘Use X software!’

My life got immensely easier when I figured out I did not need any features ZFS brought to the table, and I did not need any of the features K8s brought to the table, and that less is absolutely more. I ended up doing MergerFS with a proper offsite backup method because, well, it’s shockingly low-complexity.

And I ended up doing Docker with a bunch of compose files and bind mounts, because it’s shockingly low-complexity. And it’s just running on Debian, instead of some OS that has a couple of layers of additional software to make things “easier” because, again, it’s low-complexity.

I can re-deploy the entire stack on new hardware in about ~10 minutes (I’ve tested this a few times just to make sure my backup scripts work), and there’s basically zero vendor tie-in or dependencies that you’d have to get working first since it’s just a pile of tarballs and packages from the distro’s package manager on, well, ANY distro.

Because I don’t sit down at my Linux destop and feel like the product. There’s no ads or suggestions or popups or apps installing themselves or shit copying my files around in ways I didn’t really want or AI bullshit or anything even remotely suggesting I buy more shit, just… whatever the fuck it is I was intending to do.

The value in not having my computer act like a damn slot machine trying to get me to insert more quarters is, frankly, immense.