The currently existing infrastructure for standard datacenters with normal capacity for heating and cooling are just fine for basic computer and storage.

All the new outfits builds are being built very specifically for inference compute, which they are only doing because it’s less hassle than retrofitting existing facilities, and they think they can trick/screw taxpayers into footing the bill if new facilities are built.

It’s a scam from top to bottom.

Ban all new datacenters as fast as possible and shut this shit DOWN

No gaming distro outperforms any other distro by any measurable means a user would notice.

…k

5G was mostly about cramming more connections into the spectrum and expanding broadcast range (as well as some other things), but it wasn’t just about node speed on the network.

You probably shouldn’t use btrfs for swap unless you understand the heavy limitations on doing so. For starters, you didn’t disable CoW when creating, so I’m assuming you don’t know the issues involved.

Aside from that, I can say Void is still pretty Alpha, regardless of the claims. I messed with a bit just to see if it was worth it for single-purpose use-cases (they make this claim), and it’s just not there, unfortunately. I believe they aim to be a rock-solid alternative to Alpine with a more simple interface, but as you noted, they are nowhere there.

I also had a TON of issues with XBPS, and they need some serious work there. Duplicate packages, update issues, orphaned packages…etc. If they are serious, they need to put more effort into improvements, and also communicating the actual status of their project. Seems they are currently failing in both regards.

If you ever need more reasons to avoid Ubuntu…

Or set fire to delicate fabrics, wallpaper, or other potentially flammable surfaces a mosquito might be near or on.

If you had authenticated within a few minutes prior to that for another action, it probably would not have asked.

Shattered Pixel Dungeon, OpenTTD, or Tux Kart.

I don’t think it could possibly be measured because it’s something like: (file size ÷ block size) * num_writes

So it entire depends on the types of files, how often you’re utilizing writes to disk…etc. I just wouldn’t worry about it. If you REALLY want to estimate the tax: use iostat to check the number of writes on the drive in the last 24 hours, THEN enable online defrag and check it again in 24 hours. See what the difference is.

It really doesn’t matter for HDD though. Barely probably matters for SSD.

It should be a default, but I can see why it would be disabled for SSDs to prevent using cycles unnecessarily. If you’re using HDDs, check and see if it’s enabled.

Either way, unless you’re REALLY needing some minor performance improvements out of your disks, it shouldn’t make a huge difference.

Oops, you’re right. ZFS doesn’t have that.

There is no “normal” amount of fragmentation on modern filesystems that do things like CoW. That’s kind of the point.

If you’re reading and writing large files with a consistent amount of I/O, you’re going to have a higher amount of fragmentation because of the nature of CoW. This is by design. This doesn’t mean anything is wrong with the filesystem, just that peak performance soon after writing is not achieved. Btrfs and ZFS do online defrag and deferred scheduling of tasks for it to allow for EVENTUAL consistency as far as contiguous block forms go. The more free space you have, the sooner it will become cleaner.

Possibly NTSYNC changes finally being let off the leash.

If you’re this lacking in confidence of your skills, you may have other issues to work out…

Lolol.

Your last line. Saying exactly what I’m saying, dawg.

Heel yaw 👊

Why is there a question mark in the title? We already know the answer.