- Видео 148
- Просмотров 277 967
Oxide Computer Company
США
Добавлен 10 май 2021
The only Cloud Computer you can own.
Oxide and Friends 10/14/2024 -- Unshrouding Turin (or Benvenuto a Torino)
RE-UPLOADED
George Cozma of Chips and Cheese joined Bryan, Adam, and the Oxide Friends to talk about AMD's new 5th generation EPYC processor, codename: Turin. What's new in Turin and how is Oxide's Turin-based platform coming along?
Notes: github.com/oxidecomputer/oxide-and-friends/blob/master/2024_10_14.md
Context: mastodon.social/@bcantrill/113302500991597856
George Cozma of Chips and Cheese joined Bryan, Adam, and the Oxide Friends to talk about AMD's new 5th generation EPYC processor, codename: Turin. What's new in Turin and how is Oxide's Turin-based platform coming along?
Notes: github.com/oxidecomputer/oxide-and-friends/blob/master/2024_10_14.md
Context: mastodon.social/@bcantrill/113302500991597856
Просмотров: 1 098
Видео
Oxide and Friends 9/30/2024 -- Querying Metrics with OxQL
Просмотров 2,2 тыс.28 дней назад
Bryan and Adam were joined by Oxide colleague, Ben Naecker, to talk about OxQL the Oxide Query Language we've developed for interacting with our metrics system. Yes, another query language, and, yes, we're DSL maximalists, but listen in before you accuse us of simple NIH! Context: mastodon.social/@bcantrill/113227184081944198 More Context: rfd.shared.oxide.computer/rfd/0463 Notes: github.com/ox...
Oxide and Friends 9/23/2024 -- RTO or GTFO
Просмотров 1,8 тыс.Месяц назад
With Amazon's return to office (RTO) mandate in the news, Bryan and Adam revisit the topic (it's been 2.5 years since last time!). Are in-office epiphanies real or is RTO fueled by nostalgia, fear... and finance? Context: mastodon.social/@bcantrill/113187567831760048 Notes: github.com/oxidecomputer/oxide-and-friends/blob/master/2024_09_23.md
Oxide and Friends 9/16/2024 -- Reflecting on Founder Mode
Просмотров 1,2 тыс.Месяц назад
With some time passed, Bryan and Adam offer a non-hot take on Paul Graham's "Founder Mode" post. While there is plenty to quibble over, there's also the kernel of an important idea: how to balance experience, novel thinking, and limited time? Also stay tuned as they share a years old "ego con". Context: mastodon.social/@bcantrill/113142872987395706 Notes: github.com/oxidecomputer/oxide-and-frie...
Oxide Compute Sled - Gimlet rear tour
Просмотров 949Месяц назад
Bryan Cantrill tours the rear blind-mate system of Gimlet, the first and current generation of Oxide Compute Sled equipped with AMD Milan processors. Shot on Apple Vision Pro at Oxide HQ. We've got a podcast episode with more info on how the rear cabling system works! share.transistor.fm/s/7258e2b5
Introduction to Oxide's Compute Sled - Gimlet
Просмотров 2,2 тыс.Месяц назад
Bryan Cantrill introduces Gimlet, the first and current generation of Oxide Compute Sled equipped with AMD Milan processors. Shot on Apple Vision Pro at Oxide HQ.
Oxide and Friends 8/24/2024 -- RFDs: The Backbone of Oxide
Просмотров 2,3 тыс.2 месяца назад
RFDs Requests for Discussion are how we at Oxide discuss... just about everything! Technical design, hardware component selection, changes in process, culture, interview systems, (even) chat we have RFDs for all of these, over 500 in a bit under 5 years. Bryan and Adam were joined by Oxide colleagues instrumental to RFDs, from their most prolific author to those making them more consumable. Thi...
Oxide and Friends 8/19/2024 -- Whither CockroachDB?
Просмотров 2,6 тыс.2 месяца назад
Lots of engineering decisions get made on vibes. Popularity, anecdotes-they can lead to expedient decisions rather than rigorous ones. At Oxide, our choice to go with CockroachDB was hardly hasty! Dave Pacheco joins Bryan and Adam to talk about why we choose CRDB… and how Cockroach Labs' recent switch to a proprietary license impacts that. Notes: github.com/oxidecomputer/oxide-and-friends/blob/...
Why Oxide?
Просмотров 1,1 тыс.2 месяца назад
From Bryan's Cloud Field Day 20 presentation: ruclips.net/video/ikn7ovpjdIg/видео.htmlsi=LR0Y_JrfiDktns4a
Oxide and Friends 8/12/2024 -- The Saga of Sagas
Просмотров 1,8 тыс.2 месяца назад
The Oxide control plane coordinates multiple services to do complex, compound operations. Early on, we knew we wanted to provide a robust structure for these multi-part workflows. We stumbled onto Distributed Sagas and built our own implementation in Steno. Bryan and Adam are joined by several members of the Oxide team who built and use Steno to drive the complex operation of the control plane....
Oxide and Friends 8/5/2024 -- Pragmatic LLM usage with Nicholas Carlini
Просмотров 9892 месяца назад
Oxide and Friends 8/5/2024 Pragmatic LLM usage with Nicholas Carlini
Oxide and Friends 7/24/2024 -- CrowdStrike BSOD Fiasco with Katie Moussouris
Просмотров 2,9 тыс.3 месяца назад
Oxide and Friends 7/24/2024 CrowdStrike BSOD Fiasco with Katie Moussouris
Oxide and Friends 7/15/2024 -- Heterogeneous Computing with Raja Koduri
Просмотров 2,6 тыс.3 месяца назад
Oxide and Friends 7/15/2024 Heterogeneous Computing with Raja Koduri
Oxide and Friends 7/8/2024 -- Innovation tokens with Charity Majors
Просмотров 1,2 тыс.3 месяца назад
Oxide and Friends 7/8/2024 Innovation tokens with Charity Majors
Oxide and Friends 6/24/2024 -- Is NVIDIA like Sun from the Dot Com Bubble?
Просмотров 2,8 тыс.4 месяца назад
Oxide and Friends 6/24/2024 Is NVIDIA like Sun from the Dot Com Bubble?
Oxide Sled Fan Assembly Tour - Gimlet
Просмотров 2 тыс.4 месяца назад
Oxide Sled Fan Assembly Tour - Gimlet
Oxide and Friends 6/3/2024 -- Musing with Changelog's Adam Stacoviak
Просмотров 1,7 тыс.4 месяца назад
Oxide and Friends 6/3/2024 Musing with Changelog's Adam Stacoviak
Oxide and Friends 5/27/2024 -- Rebooting a datacenter: A decade later
Просмотров 2,7 тыс.5 месяцев назад
Oxide and Friends 5/27/2024 Rebooting a datacenter: A decade later
Rack-Scale Security Attestation for the Oxide Cloud Computer
Просмотров 5 тыс.5 месяцев назад
Rack-Scale Security Attestation for the Oxide Cloud Computer
Oxide and Friends 5/20/2024 -- Bookclub: How Life Works by Philip Ball
Просмотров 9175 месяцев назад
Oxide and Friends 5/20/2024 Bookclub: How Life Works by Philip Ball
Oxide Server Sled Rear Tour - Gimlet
Просмотров 2,7 тыс.5 месяцев назад
Oxide Server Sled Rear Tour - Gimlet
The Curiously Quiet Cloud Computer
Просмотров 3,7 тыс.5 месяцев назад
The Curiously Quiet Cloud Computer
Oxide and Friends 4/24/2024 -- All we have to fear is FUD itself
Просмотров 1,6 тыс.6 месяцев назад
Oxide and Friends 4/24/2024 All we have to fear is FUD itself
Oxide and Friends 4/15/2024 -- A Baseball Startup with Paul Freedman and Bryan Carmel
Просмотров 6216 месяцев назад
Oxide and Friends 4/15/2024 A Baseball Startup with Paul Freedman and Bryan Carmel
Oxide and Friends 4/8/2024 -- Discovering the XZ Backdoor with Andres Freund
Просмотров 6 тыс.6 месяцев назад
Oxide and Friends 4/8/2024 Discovering the XZ Backdoor with Andres Freund
Oxide and Friends 4/1/2024 -- Cultural Idiosyncrasies
Просмотров 1,8 тыс.6 месяцев назад
Oxide and Friends 4/1/2024 Cultural Idiosyncrasies
Oxide and Friends 3/25/2024 -- Adversarial Machine Learning
Просмотров 1,2 тыс.7 месяцев назад
Oxide and Friends 3/25/2024 Adversarial Machine Learning
Please check the date in the title of the episode :-)
oops!
Hello from Turin
Which episode is Bryan talking about at 1:39:05?
Thanks for asking! share.transistor.fm/s/65a10522
Beer Tunnel
We've spent the last 60 years - since Dennis and Van Horn - re-implementing capability security badly and re-discovering that these techniques happen to work shockingly well.
System 76 can make Coreboot work on modern processors.
So much respect for 0xide's communication around AI. If you have a use case, here's how easily you can do it, otherwise, there's not a shovel in sight.
I have to say, the sheer speed of provisioning and setting up Helix, really shows off how much Ooomf! is behind the Rack.
Sounds a bit like kql from Microsoft
UNIX is the outgrowth of that which exists in all of us.
If a SQL query is taking too long, then either the index is defined wrongly or there is no index, in either case the query is doing (a) full table(s) scan.
Is that "not invented here" I hear at 06:56? From anyone else, no surprise, but from you guys, the students of history?
Yep, you did reinvent the wheel, and not in a good way. Use ANSI SQL.
We’ll get on that!
Glad to hear it. RUclips comments are by far the best source of software design wisdom. Always have been, always will be.
Piping tables reminds me of Power Query M code
M3QL was a pipe based query language for M3 TSDB eventually abandoned for PromQL.
I have to say, the audio has been consistently good last 4-6, 7 live streams. Levels have been good.
Oh interesting you're not compiling OxQL to SQL.
There is no on time, only early or late. Except for Gandalf, he arrives precisely when he intends to.
Oh God now I'M triggered. I'm a Deuce Deuce rider too. We have enough high-powered engineering talent in the Bay Area to turn this into a train paradise, if we wanted to! How do we make that happen? IDK
Step Nr.1 is to realize that trains don't operate in a vacuum. To make trains effizient, everything around the trains need to be reconsidered. First up, changing land use pattern and zoning. This is fundamental and the primary reason the US is fundamentally failing at doing great transit, even when spending lots of money. When your train station is surrounded by highways, stroads and parking lots, it can't succeed. Second, trains need a feeder system, walking, bikes and buses. Buses need to be have a coordinate time table with the train, clock face scheduling. In order to do this buses need to be given effective priority, that means removing car lanes and parking spots, in addition to signaling priority and fundamental road redesign around actual modern smart road engineering principles, rather then 60s fake-science. Then also redesigning roads to make them appropriate for real bicycle use as transportation. The problem is it doesn't require some new engineering, or brilliant startup, it requires no technology that wasn't already in use in the 1960s. Its purely a social and bureaucratic problem. But don't reinvent the wheel, just adopt Dutch road engineering and safety standard, Japannase zoning laws and Swiss train management practice. Don't get any Silicon Valley startups involved, simply go to a big European or Asian company and let them do it. You don't need more tech bros reinventing trains. So yeah, just change your whole society I guess. Good luck.
Some great takeaways from this! Was a good one to reflect on my own style of 'management' as I'm trying to navigate keeping a foot in the technical details while taking on more senior managerial type work at the startup I'm at. I think Clarity + Trust is a really great lens to use to decide how to get involved. I don't have the time or energy to micromanage, but I can sometimes be a little too hands-off. I've seen how people, particularly Engineers, can get caught on certain ideas and head down paths that don't really make practical sense to do. I'm not sure if you've covered it in a past episode, but I'd love to hear more about how Oxide manages to set the direction for individuals and how you make sure you're building the right thing, and delivering the right work, on a day to day basis. Like RFDs obviously seem fairly core to setting the direction, but how do you then make plans around that and deliver on it? At my startup we're basically mandated from up-high to be doing sprints and planning in Jira and all that. I try and keep it as low touch as possible while still giving the visibility that the execs need, but I find myself more and more saying "Can you make a ticket for that?" "Is there a ticket for that?" It's our only method for tracking the ridiculous amount of work we need to deliver on, without dropping it all. Also, I loved the detour into the elaborate prank on Dave Hitz
If I ever start a business, I'll probably be in Flounder Mode. Lying at the bottom, both eyes fixed in the same direction. 🐠
Was really hoping you would cover this. Thanks!
I don't know anythibg about servers. How do server CPUs work? Are they x86? Can they run CLI desktop programs the same way?
These are an AMD Milan CPU, x86-64 like many desktops/laptops, but with a lot more cores. I admit I don't know what operating systems they ship or support, but my guess is that customers will expect to run the same Linux and windows server workloads their off-the-shelf servers do. Yes, in theory anything that can run unattended is a good candidate for running on a server.
Now all the jargon is made flesh. Now I know the diff between Gimlet and Scrimlet. Very Nice.
But where's the VGA connection?! 😱
These “neck down” framings are a wise cinematographic decision.
This weird little company has some surprisingly good marketing material
😍
superb design would like to see a better video i.e. hi-res, closeups and better lighting
Very demure, very mindful!
It's such a clean design! Looks like Oxide EEs and MEs are allowed to talk to each other, directly. 😅 I especially like the minimal use of cabling.
Easily replaceable temp sensors on little daughter boards is a great idea.
it looks too big for what it is, should have 2 cpus for the size
Well, that's a socket SP-3, so potentially you're looking at 64 procs right there. Socket count doesn't really matter as much as it once did.
@@JohnVance Agreed, especially given the memory bandwidth available to one socket today.
To whom do I send the nickel?
Why 54v?
Higher DC voltage means less current, so (generally) for power delivery/connectors you want higher voltage if you can. The upper bounds on that voltage are often between (1) regulatory definitions of what "low voltage" is (this legal limit varies between 48v to 60v depending on context), (2) what your DC-DC converters can convert cheaply/efficiently, and (3) amperage/heat limits of your power connectors
@@admalledd 48v seems like the standard value for low voltage that I’ve heard of, but i dont know much about DC in the data center. Is 54v a standard value there?
Disclaimer: I work for Oxide According to UL 62368, an ES1 circuit is the lowest hazard level covered by the standard and is generally equivalent to SELV (Safety Extra Low Voltage) and the voltage limit to be classified as ES1 is 60VDC. 54.5V is approximately 9% below this limit, which allows for voltage variation due to line/load/etc and still be able to guarantee that the voltage will still be considered "low voltage". While 48V is standard in telecom infrastructure (many times -48V), but it doesn't hurt anything to go as high as possible here since most standard 48V power supplies designed for telecom aren't dense enough for our applications (our input DC-DC is 1300W continuous rated) and the power circuitry (such as hot swap controllers) work just fine at 54V instead of 48V. The higher voltage you go, the lower your resistive losses are (which go up with the square of current). Some of the more recent Open Compute (ORV3) designs use 50.5V instead of 54V, but we haven't found anything that would make us go that route and 54.5V is still a "standard" voltage for the parts we would need.
@@EricAasen-Oxide OSHA requires additional safety requirements for anything about 50v so a lot of industries just go 48v to stay under that limit. Plus it is easily split into other common voltage levels (24v, 12v, 6v, 3v, and 1.5v) which is proballly useful for sourcing parts.
@@AndrewMorris-wz1vq As I understand the OSHA requirements, those are more around guarding to prevent accidental contact. Our system is touch-safe and nothing over 12V can be reached while it is powered. The busbar is also touch safe even when something is removed from the rack for service. The limit of 60V from the UL regulation has more to do with the minimum required isolation barriers you need between hazardous voltages (such as those above the ES1 limit of 60V) and lower voltages or accessible parts (things that can be touched by a user during normal operation) that might become energized with a hazardous voltage if there was a fault condition. This is the reason there are quite a few power supply designs now that are not isolated and go from 48 or 54V down to either an intermediate bus of 6-12V or direct from 54V to the very low (0.5-1.5V) voltages a large ASIC like a processor or GPU needs in one conversion step. This is done on designs like the AI accelerators from AMD and NVIDIA because of the extreme power levels they need in exceedingly small spaces. Of course there are tradeoffs there, but if those designs had to be isolated, they would not be as dense as they are.
Superb!
21:04 "The content of a note may be any thought, suggestion, etc. related to the software or other aspect of the network. Notes are encouraged to be timely rather than polished. Philosophical positions without examples or other specifics, specific suggestions or implementation techniques without introductory or background explication, and explicit questions without any attempted answers are all acceptable. The minimum length for a note is one sentence." my heart fluttered,,,,,
1:22:32 "owning your strategic weirdness" is amazing. "We didn't even know what they were going to be." There's so few companies that have such concrete backbones, artifacts where institutional knowledge lives and grows. Theres a lot of telling stories here about this RFDs, but man, it all revolves around such a fabulous incredible case of how engineering can work, how information can exist, that so few companies utterly lack. And this just seems like such the better world. Writing things down & letting people see is such a superpower!
Agree fully. The text-heavy approach is also a nice, passive protection against "glib talkers" that ruin companies by convincing the gullible majority of their hare-brained ideas and manage to practically silence employees with actual, domain specific knowledge. It's easy to get steam-rolled (as an introvert) by glib-talkers in a meeting but let these charlatans put their arguments to paper and be astounded how little substance there is after minimal amounts of scrutiny.
"is this a gen x thing?" 😂 "isnt that a boomer thing?" im dyinggg
Germany is accepting Bryan's apology. This time.
it would be interesting to see if there are any abandoned RFDs suitable to be made public -- i would love to read about an alternate-reality Oxide solving different subsets of problems
Bryan Cantrell is ahead of his time
Wow, Dave is humble. Bryan sounds like a great boss. Cheers from Canada.
Too bad you guys didn't know about Vertica. Vertica solved the replication, sharding and clustering problem on top of Postgres, and it does what it says on the tin.
Could you talk about how you sorted out logistics like coming up with the sales / licensing / support contract for customers to sign when they buy the product?
I wanted to like like CoackroachDB but its PL/pgSQL support is incredibly immature.
Curious how many of Postgres sharp edges still exist or have been solved in Postgres-compatible AWS Aurora.
Great episode, and a cautionary tale of the pitfalls of writing software that's so robust that no one needs to upgrade from the open-source version to the new proprietary version.
This seems kinda like structured concurrency, mirrored in server land.