There are also the hobbyists who cool their motherboards with liquid nitrogen so they can clock them very fast. I think that a major issue with all liquid cooled systems is that the coolant requires more maintenance than the underlying computer. It also represents a common point of failure that can take everything else down. Air cooling may be crude - but it is relatively robust.
Before Cray Research used Fluorinert, he used Freon in two systems: CDC 6600/6400 and the CDC 7600.
And BTW: Could not get a similar cooling system working for what was to be the CDC 8600. That failure is why Cray left Control Data and formed
what would be really interesting is if someone (Intel) promoted a standard location for a cold plate on a standard 1U. vendors could arrange heatpipes inside the chassis however they liked, and the rack vendor would be responsible for circulating coolant through the plates that mated with the chassis plates...
modular, non-proprietary and not requiring a coolant hookup for each server.
Technology triumphs! Let's try this:
I have been continually surprised that a liquid-based cooling sysem has not been put in place for servers: much more efficient than cooling with air.
(I am also a little disappointed there is not opportunity to edit/delete a post when errors are made.)
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.