Software engineer also at @dap@hachyderm.io

Joined February 2011
Surprising absolutely no one, @ahl and I are going to pick this up on the next Oxide and Friends, where we'll be joined by @dapsays to discuss our history and disposition with respect to CockroachDB. Join us: Monday, 5p Pacific! discord.gg/QrcKGTTPrF?event=…
2
15
2
81
28,895
RFD 508: Whither CockroachDB? rfd.shared.oxide.computer/rf…
1st coffee: i see @bcantrill commits to forking cockroach db: news.ycombinator.com/item?id… hoping there will be an @adamhjk thread about cockroach license change before 2nd coffee time.
11
42
10
246
141,488
In building Omicron, the control plane at Oxide, we took inspiration from @caitie's resurrection of sagas, a 1980s-era database idea. On Monday, @ahl and I will be joined by @mycoliza and @dapsays to talk about our saga with sagas. Join us, 5p Pacific! discord.gg/QrcKGTTPrF?event=…
11
1
84
19,683
i've spent the last four months or so working on rewriting the parts of the @oxidecomputer control plane responsible for managing the lifecycle of VM instances on the rack, and i have to say, seeing this branch finally merge today feels *really* good: github.com/oxidecomputer/omi…
4
9
2
122
16,936
When we built the Oxide Cloud Computer, we wanted to rectify (no pun intended!) a major issue with traditional servers: power supply + efficiency. Legacy infrastructure is wildly inefficient - each traditional server is individually plugged into power supplies converting AC to
6
9
1
156
21,148
Dave Pacheco retweeted
We’ve been working on this whole ecosystem of OpenAPI related Rust facilities—server framework, linter, client codegen, CLI codegen, test framework, etc. It’s got all the fussiness and brevity that I love about Rust. I’m looking forward to talking about it in Austin!
3
27
3,140
If you're attending @QConSF next week and are interested in the challenges of networking in a rack-scale computer, you will want to be sure to check out the talk by Oxide engineer @rgoodfel!
1
14
36
7,091
Dave Pacheco retweeted
Learn about an independently developed open source P4 compiler built by a team at @oxidecomputer. Check out the blog, video and slides for all the details. | bit.ly/3KAeDr6 #P4 #OpenSource
8
2
28
6,825
How it started.. how it's going..
14
55
7
613
59,069
Replying to @SFGate
@SFGate this article reports that an earthquake happened today at 4:34pm local time (i.e., the future). From the linked USGS page it looks like it was 1634 UTC, which is 8:34am local time.
1
2
226
Wow, great to see this. We spent much of 2017 debugging and working around this problem at Joyent cc @bcantrill
Thomas Munro (@MengTangmu): Reducing replication lag with IO concurrency in Postgres 15 postgr.es/p/5s1
3
5
15
The amusing part was asking at PgConf SF about this problem (which we hadn’t found documented anywhere) and being referred to the work we had done on pg_prefaulter
1
7
Dave Pacheco retweeted
On the back of the enthusiastic response to @bcantrill's talk at OSFC "I have come to bury the BIOS, not to open it - The need for holistic systems", our space Monday was devoted to holistic boot and the approach we've taken at @oxidecomputer youtube.com/watch?v=KItJzncv…
5
5
31
If you are wondering about our approach to platform initialization, see this excellent explanation from @dave_universetf 👇🧵
This Post is from an account that no longer exists. Learn more
3
23
1
96
a debugging manifesto
85
1,801
206
6,713
We are shipping our first racks by the end of the year, and we are very excited to get our new website up -- including many more details about what we've done and why. Awesome work, @lenjaminbeonard and crew! oxide.computer
12
43
4
207
Dave Pacheco retweeted
Horrifyingly, it apparently needs to be said: many abortions are -- in fact -- wanted pregnancies. To compound a mother's grief by outlawing the medical procedure that she needs to assure her own health is unconscionable and inhumane.
8
19
1
162