Thanks for the link.
It seems HPE bought TidalScale
in December 2022
…let’s see, what remains…
Mr. Morgan wrote in the article:
“If software-defined NUMA clustering finally does take off – and we think it could be an important tool in the composable infrastructure toolbox – then TidalScale could become an acquisition target.”
3 months later:
Sold!
…so I could irconically say:
“Thank you Mr. Morgan for making HPE aware of this…now it’s gone…” 🙂
…or:
“Good view onto the market. Well done Sir.”
->Someone in the comments mentions Popcorn Linux and the Beowulf Cluster, but according to the list at
https://en.wikipedia.org/wiki/Single_system_image
(I normally do not use WikiPedia, as it might present in 5 minutes anything completely different as it does at the moment, and, neither of both might be true…but in this case, as a short startup…)
there is not much left…
]]>Sure.
WHY AREN’T THERE SOFTWARE-DEFINED NUMA SERVERS EVERYWHERE?
https://www.nextplatform.com/2022/09/12/why-arent-there-software-defined-numa-servers-everywhere/
vaxcluster invented a whole ton of incredible HA and distributed systems technology that stood above a lot of its peers for decades. It did so with 32MB of ram or less. However, the rest of the world has now copied those successes, and the technology you remember from vaxcluster has been pretty well adopted by lots of the things we’re all used to: kubernetes, kafka, opensearch, etc.
The one thing you really can’t get in the land of open-source, is a truly huge-scale distributed sql database. I guess that’s why oracle and company are able to keep charging so much money for them.
Because the full price list was not available yet, and that was the comparison that I was given as an example.
]]>And knowing how Oracle loves to make money, the price drop is stunning, and just goes to show how much consolidation they’re getting on the backend. Note how it doesn’t talk at all about dedupe or compression on the storage side, and I strongly suspect they’re using that as well.
]]>Because it doesn’t sound cool enough.
]]>Since exascale is tied to a fixed power of ten that will change, why not just say cloudscale from the beginning?
]]>