zlacker

>>g-mork+(OP)
I still don't understand the "data center in space" narrative. How are they going to solve the cooling issue?

>>Saline+v3
Cooling a datacenter in space isn't really any harder than cooling a starlink in space, the ratio of solar panels to radiating area will have to be about the same. There is nothing uniquely heat-producing about GPUs, ultimately almost all energy collected by a satellite's solar panels ends up as heat in the satellite.

IMO the big problem is the lack of maintainability.

>>sebzim+94
I think that it's not just about the ratio. To me the difference is that Starlink sattelites are fixed-scope, miniature satellites that perform a limited range of tasks. When you talk about GPUs, though, your goal is maximizing the amount of compute you send up. Which means you need to push as many of these GPUs up there as possible, to the extent where you'd need huge megastructures with solar panels and radiators that would probably start pushing the limits of what in-space construction can do. Sure, the ratio would be the same, but what about the scale?

And you also need it to make sense not just from a maintenance standpoint, but from a financial one. In what world would launching what's equivalent to huge facilities that work perfectly fine on the ground make sense? What's the point? If we had a space elevator and nearly free space deployment, then yeah maybe, but how does this plan square with our current reality?

Oh, and don't forget about getting some good shielding for all those precise, cutting-edge processors.

>>tavave+97
Why would you need to fit the GPUs all in one structure?

You can have a swarm of small, disposable satellites with laser links between them.

>>pantal+9a
Because that brings in the whole distributed computing mess. No matter how instantaneous the actual link is, you still have to deal with the problems of which satellites can see one another, how many simultaneous links can exist per satellite, the max throughput, the need for better error correction and all sorts of other things that will drastically slow the system down in the best case. Unlike something like Starlink, with GPUs you have to be ready that everyone may need to talk to everyone else at the same time while maintaining insane throughput. If you want to send GPUs up one by one, get ready to also equip each satellite with a fixed mass of everything required to transmit and receive so much data, redundant structural/power/compute mass, individual shielding and much more. All the wasted mass you have to launch with individual satellites makes the already nonsensical pricing even worse. It just makes no sense when you can build a warehouse on the ground, fill it with shoulder-to-shoulder servers that communicate in a simple, sane and well-known way and can be repaired on the spot. What's the point?

>>tavave+yd
Starlink already solved those problems, they do 200 GBit/s via laser between satellites.

And for data centers, the satellite wouldn't be as far apart as starlight satellites, they would be quite close instead.

>>pantal+Km
No they didn't. 200Gb/s is 25GB/s, so... They could run 1/36th of a single current-gen SXM5 socket. Not even any of the futuristic next-gen stuff. 25GB/s is less than the bandwidth of one X16 PCIe3 socket. And that's already assuming the best-case scenario, and in reality trying to sync up GPUs like that would likely have loads of other issues. But even just the sheer amount of inter-GPU bandwidth you need is quite extreme. And this isn't some point-to-point routing like Starlink trying to get data from A to B, this is maintaining a network of interconnected systems that need to communicate chaotically and with uneven demand.