←back to thread

How oxide cuts data center power consumption in half

(oxide.computer)
195 points tosh | 5 comments | 21 Nov 24 18:12 UTC | HN request time: 0.852s | source
Show context
farawayea ◴[21 Nov 24 20:51 UTC] No.42208533[source]▶
Their tech may be more than adequate today. Bigger businesses may not buy from a small startup company. They expect a lot more. Illumos is a less popular OS. It wouldn't be the first choice for the OS I'd rely on. Who writes the security mitigations for speculative execution bugs? Who patches CVEs in the shipped software which doesn't use Rust?
replies(6): >>42208689 #>>42208888 #>>42208978 #>>42209356 #>>42209429 #>>42209882 #
AlotOfReading ◴[21 Nov 24 21:10 UTC] No.42208689[source]▶
The answer to "who does X" is Oxide. That's the point. You're not going to Dell who's integrating multiple vendors in the same box in a way that "should" work. You're getting a rack where everything is designed to work together from top to bottom.

The goal is that you can email Oxide and they'll be able fix it regardless of where it is in the stack, even down to the processor ROM.

replies(2): >>42208776 #>>42210376 #
1. toomuchtodo ◴[21 Nov 24 21:19 UTC] No.42208776[source]▶
This. If you want on prem cloud infra without having to roll it yourself, Oxide is the solution.

(no affiliation, just a fan)

replies(1): >>42208948 #
2. carlhjerpe ◴[21 Nov 24 21:39 UTC] No.42208948[source]▶
If you want on prem infra in exactly the shape and form Oxide delivers*

I've read and understood from Joyent and SmartOS that they believe fault tolerant block devices / filesystems is the wrong abstraction, your software should handle losing storage.

replies(3): >>42209046 #>>42209292 #>>42223389 #
3. ◴[21 Nov 24 21:50 UTC] No.42209046[source]▶
4. eaasen ◴[21 Nov 24 22:21 UTC] No.42209292[source]▶
We do not put the onus on customers to tolerate data loss. Our storage is redundant and spread through the rack so that if you lose drives or even an entire computer, your data is still safe. https://oxide.computer/product/storage
5. panick21_ ◴[23 Nov 24 19:48 UTC] No.42223389[source]▶
They have partly changed their position on that. You can listen to their podcast on their distributed block storage solution.