Live data from Hacker News

Oxide at Home: Propolis Says Hello

artemis.sh

81–90 of 112 posts

Re: Oxide at Home: Propolis Says Hello

#81
post #60

Earlier quoted context omitted.

The podcast is awesome. Wish they would continue with more episodes!

They've been doing Twitter Spaces for several months now, with recordings and show notes here: https://github.com/oxidecomputer/twitter-spaces Disclosure: I was the main speaker on one of their spaces.

Whaaaaaaattt. And I've been here waiting for a new podcast, like an idiot... when they had this... Thanks for the info!

Re: Oxide at Home: Propolis Says Hello

#82

Earlier quoted context omitted.

What's kind of messed up, at least for tiny companies like mine, is that renting an ugly PC-based dedicated server from a company like OVH is currently cheaper than paying for the equivalent computing power (edit: and outgoing data transfer) from a hyperscale cloud provider like AWS, even though the hyperscalers are probably using both space and power more efficiently than the likes of OVH. My cofounder will definite…

> renting an ugly PC-based dedicated server from a company like OVH is currently cheaper than renting the equivalent computing power from a hyperscale cloud provider like AWS That's not surprising, you're basically paying for scalability. An idle box doesn't even necessarily "waste" all that much energy if it's truly idle, since "deep" power-saving states are used pretty much everywhere these days.

Sure, the CPU may enter a power-saving state, but presumably for each box, there's a minimum level of power consumption for things like the motherboard, BMC, RAM, and case fan(s). The reason why AWS bare-metal instances are absurdly expensive compared to OVH dedicated servers is that AWS packs more computing power into each box. So for each core and gigabyte of RAM, I would guess AWS is using less power (edit: especially when idle), because they don't have the overhead of lots of small boxes. Yet I can have one of those small boxes to myself for less than I'd have to pay for the equivalent computing power and bandwidth from AWS.

Re: Oxide at Home: Propolis Says Hello

#83
post #71

Earlier quoted context omitted.

I think the intention is that those people are better served with consolidated cloud providers? -- or even single digits of physical colocated servers. It would be nice to have a known pricepoint from a cloud provider which once exceed you ask the question: "Should we buy a rack and COLO it?" Even if the answer is "no" it's still good to have that option. --- The thing is: Datacenter technology has moved on from 2011…

What's kind of messed up, at least for tiny companies like mine, is that renting an ugly PC-based dedicated server from a company like OVH is currently cheaper than paying for the equivalent computing power (edit: and outgoing data transfer) from a hyperscale cloud provider like AWS, even though the hyperscalers are probably using both space and power more efficiently than the likes of OVH. My cofounder will definite…

You’re amortising a lot of software developers and sysadmins with your AWS bill. It’s also in-trend so a bit premium.

They’re not reasonably equivalent. But I don’t doubt that Amazon is laughing to the bank still.

Re: Oxide at Home: Propolis Says Hello

#84

Earlier quoted context omitted.

> renting an ugly PC-based dedicated server from a company like OVH is currently cheaper than renting the equivalent computing power from a hyperscale cloud provider like AWS That's not surprising, you're basically paying for scalability. An idle box doesn't even necessarily "waste" all that much energy if it's truly idle, since "deep" power-saving states are used pretty much everywhere these days.

Sure, the CPU may enter a power-saving state, but presumably for each box, there's a minimum level of power consumption for things like the motherboard, BMC, RAM, and case fan(s). The reason why AWS bare-metal instances are absurdly expensive compared to OVH dedicated servers is that AWS packs more computing power into each box. So for each core and gigabyte of RAM, I would guess AWS is using less power (edit: especi…

Interestingly, I believe that unused DIMM modules could be powered down if the hardware bothered to support that. Linux has to support memory hotplug anyway because it's long been in use on mainframe platforms, so the basic OS-level support is there already. Since it's not being addressed in any way by hardware makers, my guess is that RAM power use in idle states is low enough that it basically doesn't matter.

Re: Oxide at Home: Propolis Says Hello

#86
post #49

Earlier quoted context omitted.

Possible better security/performance through better architecture?

From what I've seen so far the same architecture could be achieved on Linux (e.g. Firecracker or Intel Cloud Hypervisor). To get great performance you often need to get elbow-deep in somebody else's driver and that may be just as much work as writing your own drivers.

We don't need Linux monoculture.

Re: Oxide at Home: Propolis Says Hello

#87
post #37
post #31

Earlier quoted context omitted.

Curious... if I'm still in the "triage" bucket after 6 weeks should I assume the ship has sailed? I was really hoping to hear back one way or the other!

No, you will hear back. We're trying really hard to keep to the 6 weeks thing but sometimes we don't succeed.

I would think that startups would want to bias for people that can make good decisions quickly, within a short decision time. Perhaps hardware startups want more conservative employees?

Also in my experience, a fabulous candidate is sometimes only available for a very short time window (they either have become available due to unforeseen circumstances, or they are snapped up by a faster mover).

Is six weeks fast in your opinion?

Re: Oxide at Home: Propolis Says Hello

#88
post #60

Earlier quoted context omitted.

The podcast is awesome. Wish they would continue with more episodes!

They've been doing Twitter Spaces for several months now, with recordings and show notes here: https://github.com/oxidecomputer/twitter-spaces Disclosure: I was the main speaker on one of their spaces.

TIL.

On one hand I'm excited at the new content but a bit weird they way they stealth shutdown the podcast and started the twitter spaces thing up without saying anything or updating their homepage. Even their twitter feed only mentions the twitter space a couple of times (and doesn't appear to link to the archive).

Re: Oxide at Home: Propolis Says Hello

#89

Earlier quoted context omitted.

They've been doing Twitter Spaces for several months now, with recordings and show notes here: https://github.com/oxidecomputer/twitter-spaces Disclosure: I was the main speaker on one of their spaces.

Whaaaaaaattt. And I've been here waiting for a new podcast, like an idiot... when they had this... Thanks for the info!

They are quite different from the podcasts. Wider range of topics and not as historically focused. I hope they do both in the future.

Recommendations technical:

- Twitter Space 12/13/2021 -- The Pragmatism of Hubris

- Twitter Space 12/6/2021 -- Tales from the Bringup Lab

- Twitter Space 11/29/2021 -- The Sidecar Switch

Historical:

- Docker, Inc., an Early Epitaph

- Twitter Space 7/5/2021 -- NeXT, Objective-C, and contrasting histories

- Twitter Space 5/31/2021 -- Silicon Cowboys

- Twitter Space 8/16/2021 -- The Showstopper Show

All of them are worth watching.

Re: Oxide at Home: Propolis Says Hello

#90
post #37
post #31

Earlier quoted context omitted.

Curious... if I'm still in the "triage" bucket after 6 weeks should I assume the ship has sailed? I was really hoping to hear back one way or the other!

No, you will hear back. We're trying really hard to keep to the 6 weeks thing but sometimes we don't succeed.

Thank you, that does help. I thankfully have some flexibility in my search… and I promise the other replies aren’t alt accounts!
Post reply on HN