Clustered FS and Objectstore are built on top of SAS, FCOE, iSCSI, NVMe-OF. You first have to solve the problem of packing thousands of storage devices within the signal integrity radius of the transport medium before you can start abstracting. For NVMe that radius is about 1.5 - 2 meters from the CPU socket. SAS about 5 meters. Not sure on FC, I presume a couple km.

Completely common. Like 70% of all servers sold include a RAID controller that can talk to NVMe devices. But there's a catch... They suck so badly, nobody buys the PCIe cables to connect the backplanes. The inside joke is the best way to slow down your NVMe drives is to attach them to a RAID controller. Most NVMe drives use 4 PCIe lanes. Broadcom's RAID chips let them have two lanes. Then the RAID controller connects to the CPU with 16 lanes. So the minute you exceed 8 drives (via a switched backplane), you have an intractable bottleneck.

The Broadcom 3xxx chip hit the wall first as it still did RAID partially on the controller CPU. The 4116 implemented RAID entirely in silicon, the 51xx chips took this further with a complete cache redesign, and actually ditches SAS/SATA entirely. It's NVMe only. But nobody has solved the PCIe lane bottleneck.

Via a PCIe switch backplane. They've been around for a while... Perhaps as far back as 2012...

I fully expect SAS4 to be the end... NVMe-OF will replace SAS, and the drives will plug into the crazy 800GbE switches that are available now. Not on the drawing board... Now.

T

Hear hear! These are well spoken facts.

And indeed here.

And surprisingly...here too.

For all its faults, I too find myself using it constantly. Mainly because it allows me the freedom to "try it and see" for certain design decisions or to apply a blanket refactoring to old code bases that no other refactoring tool could possibly do. Or to just crank out scripts that technically work and get you the parsed results you need but you'd never try to maintain beyond the immediate need.

Those, and others, are the reasons I still use it daily...increasingly so. I can have it bang out that script to do "whatever" is needed at the time (usually data analytics or dataset transforms or whatever). Scripts I might not have ever written on my own because it would just take too long and so instead of digging deeper into "whatever" at the time to cross check and validate assumptions, I might have just assumed.

This tooling allows me to do things I wouldn't have before. It allows me to try patterns and see how they play out without any real fear of wasting my time because it's being done FAR quicker than I would have. And in the end, I have a set of options to consider rather than just picking something up front and pushing through the grind to make it the chosen way.

But pointing it to a bug and blindly submitting that trash output...ZERO chance. Even if it works, and honestly, often it does, it's almost ALWAYS complete trash code. I can bound that trash output with more specific prompts, yes. And this does work reasonably well...but you pretty quickly get to a point where you've spent about as much time crafting those fancy prompts in that case as you might have spent just writing the code yourself.

The more specific and structured you want the output, the longer it takes to get it. It can be fast or right, but not both.

I got my hands on a 3B1 around 1990. Linux wasn't available of course, and a used Sun was just out of my reach. It was a giant box of suck. The most corporate version of Unix I've ever used. It made me pine away for the dialup guest account on Compupro's Unix Version 7 system in the east SF Bay back in the 80's...

Eventually I picked up a Sun 3/50, and later a 3/60. Then some kid in Finland posted on Usenet and well...

Are you talking about CVE? Looking back it seems like it but if so, you might be on the wrong forum here. For reference, they did define these terms.

National Vulnerability Database (NVD)
Cybersecurity and Infrastructure Security Agency's (CISA)
Known Exploited Vulnerabilities (KEV)

Which I think is fair. But they didn't bother with NIST (I assume you did know that one) or CVE cause, I dunno, they're pretty damn common place...certainly on this site. There's a point where you can assume people in your audience know some level of detail about the topic you're presenting to them. And CVE, in my opinion (IMO), certainly fits that.

Or force them to keep their constellations lower, which means the satellites have to carry more fuel to fight drag, but if they fail they'll just deorbit in a few years. You can go a bit lower and use air-breathing ion thrusters as well, and those will deorbit even faster.

The big danger is the stuff in higher orbits that takes 100-1000 years to come down.

I mean, a small online bookstore pivoted to become one of the most foundational structural elements of the internet.

Funding via pay per view? There's an Idiocracy joke in there somewhere...

I'm about done with NVIDIA. Here's to hoping Intel improves their Linux driver support... They step up their game, and I could be convinced to switch. But right now.... It's all crap.

T

Tell me you can't read without telling me you can't read.

To be clear...PoGo is *not* free. Absolutely, positively, NOT free. ;) Yeah, you're still the product for sure...but you pay dearly for that privilege. I may or may not have an addicted spouse, so I may or may not know.

(Yes, you *can* play for free...or could at one time...but you're entirely ineffective and capped at what you can actually do to the point of being worthless.)

Windmills don't kill corn. Windmills don't kill clams. They might scare some fish initially due to low frequency vibrations but they will probably adapt. The bird-killing issue is a thing but they've found that they can minimize it somewhat with different paint on the blades.

Yes there are negative issues, just like any other infrastructure project, but you have to weigh them, and you can't let your own ideological alignment get in the way.

Trump hates windmills because he hates how they look near his properties. He has a particular issue and then builds an ideological theme to support it. People get roped into ideology and stop weighing the costs and risks in favor of being a *movement*.

Opposite side of the isle it's just as bad, they're terrible at seeing the benefits of nuclear on ideological growns. They hate burning fossil fuels so bury their head in the sand at plastic incineration being more efficient and overall less carbon intensive than recycling programs.

Offshore windfarms aren't any more harmful than offshore oil rigs, and in practice offshore oil rigs are beneficial for the local ecosystem by adding a habitat (excellent fishing btw).

It's not like we didn't have police, just not what we think of as a modern police force. We had organized law enforcement consisting of sheriffs and constables, with the power to deputize when needed.

This is much the same as we didn't have organized fire brigades, instead we had government officials with the power to organize a response to fires by recruiting more manpower from the populace to fight fires.

Asking if we need a police force because we didn't previously have one is like asking if we need a fire department because previously we only had an informal volunteer fire department. These things only worked in the past because the need was small enough that we didn't have the economy of scale to support a professional firefighting or police force, but with growth, the professionalization required necessitated the formation of these things.

Also the "cops are just slavecatchers" thing is a largely made up and exaggerated talking point by the far left that they repeat ad-nauseum. The first professional police forces in the US were formed in northern cities like Boston and were decidedly *NOT* slavecatchers, but rather organized out of groups normally deputized to enforce the law, turning them into professional employees -- in much the same way a volunteer fire department becomes a full time employer in cities that grow enough to need it.

Some early southern professional police and sheriff departments *were* constituted out of slave patrols, as these were people who were often deputized, but these were not the first police departments, nor did they constitute the majority of them, not even in the south.

Why not say "School starts when the sun has been up for one hour. During these months school starts at 16:00 TAI, and in these months it starts at 17:00 TAI.

Use the time measurement consistently. Imagine "daylight saving length" where "For these months, start measuring things as one inch longer" and having to change how everything is measured..

The vast, vast majority of Americans don't live in "remote areas". They live in towns with infrastructure, and don't drive long distances except for the occasional road trip (a rarer thing these days). While the typical American daily travel experience is a longer distance than in the rest of the world, this is by virtue of car-centric infrastructure, with more people in other developed countries walking or taking public transit, but among people who *do drive* in other countries, it's not a huge difference in terms of how far people drive in a typical journey.

In terms of cold temperatures, the performance differences are vastly overstated by ICE apologists. The country with the highest EV adoption in the world is Norway, a country not exactly known for its mild winters, particularly on the coastline facing the Atlantic. I've lived in a cold climate myself and know the experience well of spending much of the year with my gasoline-powered vehicle's auxiliary heater plugged into an electric socket just to keep the vehicle from freezing, but for some reason that constant energy use was never figured into the calculations. With batteries, you know your range will go down a bit, though that is being mitigated somewhat with newer battery chemistries, and you figure that into the range of the battery capacity when you buy the vehicle.

Resale value is the only point I'll concede, but that's really more a factor of how fast the tech has been developing vs the very mature ICE technology. The exact same thing happened with early gasoline automobiles. As the tech matures you'll see the market for used EVs stabilize, and this is already happening somewhat.

An EV from ten years ago is now very usable on its old battery pack. When you buy an ICE vehicle, you look at the odometer and if it has a lot of miles on it you figure the reduced reliability into the price you're willing to pay. EVs have far more mechanical reliability, so you're more figuring in the functional range on the battery pack in the price you're willing to pay rather than the remaining lifetime on the engine.