Earlier quoted context omitted.
International space law (starting with the Outer Space Treaty of 1967) says that nations are responsible for all spacecraft they launch, no matter whether the government or a non-governmental group launches them. So a server farm launched by a Danish company is governed by Danish law just the same as if they were on the ground- and exposed to the same ability to put someone into jail if they don't comply with a legal…
What if you’re a stateless person? (Not an easy status to acquire these days, but any US citizen can just renounce their citizenship without getting a new one, for example.)
Starcloud can’t put a data centre in space at $8.2M in one Starship
231–240 of 365 posts
Re: Starcloud can’t put a data centre in space at $8.2M in one Starship
#232Earlier quoted context omitted.
I think it's likely the overall rate would be higher, and you might find you need more aggressive burn-in, but even then you'd need an extremely high failure rate before it's more efficient to replace components than writing them off.
The bathtub curve isn’t the same for all components of a server though. Writing off the entire server because a single ram chip or ssd or network card failed would limit the entire server to the lifetime of the weakest part. I think you would want redundant hot spares of certain components with lower mean time between failures.
And at sufficient scale, once you plan for that it means you can massively simplify the servers. The amount of waste a sever case suitable for hot-swapping drives adds if you're not actually going to use the capability is massive.
Re: Starcloud can’t put a data centre in space at $8.2M in one Starship
#233Earlier quoted context omitted.
https://accendoreliability.com/the-bath-tub-curve-explained/ is an interesting breakdown of bath tub curve dynamics for those curious!
Wonder if you could game that in theory by burning in the components on the surface before launch or if the launch would cause a big enough spike from the vibration damage that it's not worth it.
Re: Starcloud can’t put a data centre in space at $8.2M in one Starship
#234Earlier quoted context omitted.
https://accendoreliability.com/the-bath-tub-curve-explained/ is an interesting breakdown of bath tub curve dynamics for those curious!
Wonder if you could game that in theory by burning in the components on the surface before launch or if the launch would cause a big enough spike from the vibration damage that it's not worth it.
And then, there is of course radiation trouble.
So those two kinds of burn-in require a launch ti space anyway.
Re: Starcloud can’t put a data centre in space at $8.2M in one Starship
#235Earlier quoted context omitted.
I've had actual, real-life deployments in datacentres where we just left dead hardware in the racks until we needed the space, and we rarely did. Typically we'd visit a couple of times a year, because it was cheap to do so, but it'd have totally viable to let failures accumulate over a much longer time horizon. Failure rates tend to follow a bathtub curve, so if you burn-in the hardware before launch, you'd expect lo…
Exactly what I was thinking when the OP comment brought up "regular launches containing replacement hardware", this is easily solvable by actually "treating servers as cattle and not pets" whereby one would simply over-provision servers and then simply replace faulty servers around once per year. Side: Thanks for sharing about the "bathtub curve", as TIL and I'm surprised I haven't heard of this before especially as…
Programming and CS people somehow rarely look at that.
Re: Starcloud can’t put a data centre in space at $8.2M in one Starship
#236Earlier quoted context omitted.
I've had actual, real-life deployments in datacentres where we just left dead hardware in the racks until we needed the space, and we rarely did. Typically we'd visit a couple of times a year, because it was cheap to do so, but it'd have totally viable to let failures accumulate over a much longer time horizon. Failure rates tend to follow a bathtub curve, so if you burn-in the hardware before launch, you'd expect lo…
The original article even addresses this directly. Plus hardware returns over fast enough that you'll simply be replacing modules with a smattering of dead servers with entirely new generations anyways.
Re: Starcloud can’t put a data centre in space at $8.2M in one Starship
#237If you are out of the magnetosphere, wouldn't your data be subject to way more cosmic ray interference, to the point that its actually a consideration?
Re: Starcloud can’t put a data centre in space at $8.2M in one Starship
#238Space roboticist here. As with a lot of things, it isn't the initial outlay, it's the maintenance costs. Terrestrial datacenters have parts fail and get replaced all the time. The mass analysis given here -- which appears quite good, at first glance -- doesn't including any mass, energy, or thermal system numbers for the infrastructure you would need to have to replace failed components. As a first cut, this would re…
Appreciate the insights, but I think failing hardware is the least of their problems. In that underwater pod trial, MS saw lower failure rates than expected (nitrogen atmosphere could be a key factor there). > The company only lost six of the 855 submerged servers versus the eight servers that needed replacement (from the total of 135) on the parallel experiment Microsoft ran on land. It equates to a 0.7% loss in the…
Re: Starcloud can’t put a data centre in space at $8.2M in one Starship
#239Earlier quoted context omitted.
I've had actual, real-life deployments in datacentres where we just left dead hardware in the racks until we needed the space, and we rarely did. Typically we'd visit a couple of times a year, because it was cheap to do so, but it'd have totally viable to let failures accumulate over a much longer time horizon. Failure rates tend to follow a bathtub curve, so if you burn-in the hardware before launch, you'd expect lo…
The analysis has zero redundancy for either servers or support systems. Redundancy is a small issue on Earth, but completely changes the calculations for space because you need more of everything, which makes the already-unfavourable space and mass requirements even less plausible. Without backup cooling and power one small failure could take the entire facility offline. And active cooling - which is a given at these…
the more satellites you put up there, the more it happens, and the greater the risk that the immediate orbital zone around Earth devolves into an impenetrable whirlwind of space trash, aka Kessler Syndrome.