3 ms·
Heh, I thought "wait a minute didn't IBM do this 20 years ago and it was a total flop?" and yes, and its one of the same people involved. Cryogenic computing w
by ChuckMcM 10y ago
Heh, I thought "wait a minute didn't IBM do this 20 years ago and it was a total flop?" and yes, and its one of the same people involved.
Cryogenic computing wasn't a bust because the technology didn't work. It does. It was a bust because silicon really hates to transition between cryogenic temperatures and room temperature. If you transition it quickly (say you pull a card out of the liquid nitrogen and start working on it) it will crack as it warms up unevenly. As a result you needed anywhere from 20 to 48 hours to get a card from 'cryo' temp to 'room' temp, and while you could cool a bit faster it still took longer than just dumping it in LN2. So repairs and maintenance were multi-day affairs. Compare that to a modern AWS, Google, or Azure data center where a system fails, a tech can skate out to it with a new motherboard, pull the old one, put the new one in, and poof you're back on line in under 30 minutes.
As a result cryo computers either had to have failure rates that were so low that a repair that required transitioning the hardware through a cold/warm/cold cycle rarely happened, or you had to have enough extra hardware to support your base load while part of it was slowly going through the cold/warm/cold cycle.
I don't know how much IBM spent, but it was a lot and they never cracked that nut.
- AdamJacobMuller 10y agoIt also seems to me that even if you accept all of those things as fact and are OK with them, say in an O&G HPC workload where you cool the DC, run for a few days/weeks and then go offline to fix issues until the next run, isn't the amount of energy and cost required way higher than just having more compute resources? Ultimately its just dollars per compute and it seems highly dubious to me that supercooling your components, even if you accept high failure rates and long lead times, is going to move that needle in a positive direction.
- derefr 10y ago> Compare that to a modern AWS, Google, or Azure data center where a system fails, a tech can skate out to it with a new motherboard, pull the old one, put the new one in, and poof you're back on line in under 30 minutes. Modularity is better now than it was then. I could very much see the possibility of having pressure-sealed internally-cryo-maintained enclosures (like the pressure-sealed internally-helium WD hard drives), as hot-swappable modules with e.g. Thunderbolt 3.1 connectivity to connect the enclosure-module to your other components. This approach would work fine for, say, enclosing NVMe. And, conveniently, repair would be facilitated by the inside of the enclosure staying cold even after you yank it out of the machine. A daughterboard in a thermos! For actual DRAM DIMMs, though, you'd have to "enclose" the motherboard itself into such a module—at which point that "module" is the computer, and you're more just talking about the old blade-server paradigm of externalizing as many components as possible to live on the rack, so that the server blades could be treated as commodity parts and swapped out like any other.
- rbanffy 10y agoAs long as the gains out weight the overhead of having extra capacity to compensate for the longer repair cycles, it's still a win. You can make a unit operate in cryogenic temperatures and, when it fails, power it down and manage its cooling long enough it can be removed safely. When repaired, just re-add it and cool it down until you can safely bring it online.
- ChuckMcM 10y agoAgreed, and for 25 years IBM could not make that equation balance out. They tried a lot of different ideas. You can see some of their patents for examples. (for a fun time go to patents.google.com and search for 'cryogenic ibm' there are lots of patents)