Google principal engineer based out of Seattle. I am the technical lead for delivering the next generations of AI GPU Supercomputers to Google Cloud. Previously, I worked on the hypervisor that powers Google Compute Engine.
jonolson at google dot com
Opinions are my own, not those of my employer.
Submissions
Andromeda 2.1 reduces GCP’s intra-zone latency by 40%
cloudplatform.googleblog.com
2 points·by jsolson··0 comments
Ex-Amazonians helping teachers create and sell online courses with Everpath
geekwire.com
2 points·by jsolson··0 comments
Status of earlier Google Calendar issue
google.com
2 points·by jsolson··0 comments
App Store Update Approval: A Proposal
jon.ballisticpigeon.com
2 points·by jsolson··0 comments
We just launched Folio - A PDF reader for iPad. How can we improve it?
macOS largely _does_ bake this into the OS, and it is annoying. They also provide a way to turn it off for specific applications (including, for example, Terminal.app).
Then, if you want to know about using optical switches to connect Clos segments without a fixed spine, check out Google's "Mission Apollo" paper: https://arxiv.org/pdf/2208.10041
For most of my time here I used exclusively Chrome OS, and switched to it for personal use as well. My daily driver for years was a bright red Samsung Chromebook Galaxy (the first gen with the actual metal case). Literally none of my work is local, and it could run Secure Shell, Cider-V, and Docs as installed PWAs with their own taskbar items, etc. It was glorious.
When it finally failed in the most annoying way possible (the touch screen, which I do not use, started creating phantom clicks in the upper right corner of the display) I went looking for another Chromebook that was light, powerful, and well-built. Finding none, I now use MacBook Air and weep for the time I lose every time it needs an OS update.
This is largely where I'm ending up, but I started at the other end.
There is value in prose that carries your literal voice when the audience is _people who know you_. There is negative value in writing prose that requires the audience to _read it in your voice_ in order for it to make sense, avoid offense, or convey intent.
My prose changed first: it became plain spoken, as devoid of contextual subtlety as I could make it. My career benefitted. My spoken interactions followed.
The only thing that bothers me about it is the nagging sense that I've become so fucking boring.
I'm trying to put together what you could possibly mean by this -- rolling coal is fundamentally about spite. In isolation, nobody _wants_ their vehicle to spew black smoke. It only comes close to making sense in the context of another population (EV owners, typically, or more generally "the libs").
OpenClaw lets people live a bit dangerously, but fundamentally gives them something that they actually wanted. They wanted it so badly that they're willing to take what seem like insane risks to get it.
You're not wrong, but PnP including the configuration basis for PCI which still sits at the config space layer of the latest and greatest PCIe. That's the piece I find so significant. I work with GPUs that mostly communicate over a proprietary C2C connection, but how does the OS find them? PCI enumeration.
I don't remember if Plug-n-Play shipped with the original Windows 95 (it's certainly there in the final OSR), but that was a pretty big shift from the manual IRQ and port mapping days of DOS/Windows 3.1.
Columbo is anything but a failure, though, and the audience knows that. His genius is leveraging humility to convince killers that he's a bumbling idiot, while in reality he's onto them from the first encounter.
_Slow Horses_ came up in another thread. I'd argue that Columbo has more in common with Jackson Lamb than with Charlie Brown.
You might have even better precision if you stay away from CPU0 and also set idle=poll in your kernel command line. Lots of things (including other interrupts) often land on CPU0. It would not be my first choice for something where I wanted high timing precision.
I agree with nearly everything except your point (1).
Periodic polling is awkward on both sides: you add arbitrary latency _and_ increase database load proportional to the number of interested clients.
Events, and ideally coalesced events, serve the same purpose as interrupts in a uniprocess (versus distributed) system, even if you don't want a proper queue. This at least lets you know _when_ to poll and lets you set and adjust policy on when / how much your software should give a shit at any given time.
My first thought was "Arc'teryx will probably adopt this immediately." They (and similar brands) are already pushing as hard as they can on seamlessness or very very tight seams.
jonolson at google dot com
Opinions are my own, not those of my employer.