CrazyLikeGollum

Might be a bit late on this, but ProxMox doesn't really handle assigning threads to the e/p cores. That's handled by the kernel and as long you're running kernel version 6.1 or greater you should be good on that front.

If you really need to, you can also pin specific VMs to specific cores. So that if you've got something that always needs the performance it can always run on the p-cores and things that aren't as demanding can always run on e-cores.

That said, especially if you're over provisioning, it's probably better to let the scheduler in the kernel handle thread assignments.

And 1/2c is a pretty middle of the road escape velocity for a neutron star.

The lightest known neutron star, at 1.4 solar masses has an escape velocity of right around 1/4c, while the heaviest at 2.35 solar masses is 3/4c.

All of which assumes the neutron star isn't spinning. Equatorial bulging caused by the rotation reduces the escape velocity at the equator relative to the poles and depending on whether or not you launch with the direction of the rotation you might be able to subtract the rotational velocity from your escape velocity.

As an example, in the case of that 2.35 solar mass neutron star, it has a rotational velocity of approximately 0.24c. So of you launch with the rotation you get an escape velocity of 0.5c, whereas if you launch against it you're looking at more like 0.98c.

I fought a glorious battle against my spicy curry dinner. It was a meal fit for a warrior and it fought with honor, even on it's way out. My butthole burns FOR THE GLORY OF THE EMPIRE!

Given that nowhere in the article does it say that 14% of people exclusively play on pre-2000 hardware I don't find this that surprising.

I'm more shocked by the last statistic, 11% of American households still use fax. Fax? Fuckin' why? That's like saying people still listen to music on Edison cylinders.

If I'm reading your example right, I don't think that would satisfy three either. Three copies of the data on the same filesystem or even the same system doesn't satisfy the "three backups" rule. Because the only thing you're really protecting against is maybe user error. I.e. accidental deletion or modification. You're not protecting against filesystem corruption or system failure.

For a (little bit hyperbolic) example, if you put the system that has your live data on it through a wood chipper, could you use one of the other copies to recover your critical data? If yes, it counts. If no, it doesn't.

Snapshots have the same issue, because at the root a snapshot is just an additional copy of the data. There's additional automation, deduplication, and other features baked into the snapshot process but it's basically just a fancy copy function.

Edit: all of the above is also why the saying "RAID is not a backup" holds true.

I don't think this meets the definition of 3-2-1. Which isn't a problem if it meets your requirements. Hell, I do something similar for my stuff. I have my primary NAS backed up to a secondary NAS. Both have BTRFS snapshots enabled, but the secondary has a longer retention period for snapshots. (One month vs one week). Then I have my secondary NAS mirrored to a NAS at my friends house for an offsite backup.

This is more of a 4-1-1 format.

But 3-2-1 is supposed to be:

• Three total copies of the data. Snapshots don't count here, but the live data does.

• On two different types of media. I.e. one backup on HDD and another on optical media or tape.

• With at least one backup stored off site.

I can't speak to AI performance, but given you're stated goal of lower idle power consumption, I'd go with the 14900K, not the KS as you have listed.

Reason being the $250 price difference between the two, when the KS is just a slightly higher binning of the K with an additional 200MHz on the boost clocks. With that higher boost being something you're unlikely to practically see without a substantial and robust cooling system, I don't think it's worth the extra money.

The reason I'd go with the K over the 10940X is the lower limit on it's power consumption. The E cores are very efficient and can down clock substantially meaning it idles at really low power. The 10940X doesn't have that benefit.

Beyond that, I'd say look at IPC, per thread, per max sustainable clock of each core, to get a general out look on performance.

Note: all of the above assumes we're working within your listed options. My actual recommendation would be an AMD 7800x3d or 9800x3d.

For most things if I'm gonna be waiting more than a few weeks, I'll let myself kind of forget about it and then enjoy it whenever it happens.

That said, I didn't do that for The Wheel of Time TV show. I learned about it relatively late; a few months before release, and then spent a lot of time reading up on it, looking into the cast, watching trailers, interacting with WoT communities online, and just generally getting kind of hyped. Most people seemed pretty positive about it. It was looking like it might actually be a good adaptation of one of my favorite book series.

Then it came out and it was the single most disappointing adaptation I've seen since Eragon.

Yes, yes, and it's NT/Windows or as I've taken to calling it NT+Windows...

This point is pedantic and tired to the point that it has become an infamous copypasta.

It's also, at least as stated here, not even technically correct. A kernel is an operating system all on it's own. It just can't do much.

GNU just provides the software that the user interacts with.

Additionally, there are a number of Linux distros that are entirely free of GNU software.

Just about everyone understands what you mean when you call Linux an OS. The pedantry is unneeded.

But what about Odo's only-in-case-of-(her)-(possibly elevator related)-emergnecy girlfriend, Lwaxana?

Why should he fear power?

Isn't windows 10 end of support this year?

Also, didn't Valve commit to SteamOS 3 for PCs at some point?