The Symphonia

DECEMBER 6, 2017

The light show at the re:Play party Another re:Invent has come and gone, and us mere AWS-using mortals are now rapidly trying to sort the wheat from the chaff of a heady harvest of announcements. It’s funny to think that AWS Lambda was announced at re:Invent only 3 years ago?—?the skip to the end if you want my take on those.

Serverless 40

Serverless Lambda AWS Traffic 40

Brendan Gregg

SEPTEMBER 25, 2021

Since instances of both CentOS and Ubuntu were running in parallel, I could collect flame graphs at the same time (same time-of-day traffic mix) and compare them side by side. I happened to be speaking at a technical confering while still debugging this, and mentioned what I was working on to a processor engineer.

Speed 40

Speed Java AWS Virtualization 40

The Symphonia

MAY 22, 2018

and products like AWS Fargate have made this distinction murkier still. Finally in this first overall section it was good to be able to talk about AWS SAM and SAR?—?“Serverless AWS API Gateway , and its associated tooling, has got much, much better. I mentioned Kubernetes pod autoscaling in the original version?—?and

Serverless 40

Serverless Architecture Lambda Azure 40

VoltDB

JUNE 1, 2017

An opening scene involving a traffic jam of Viking boats and a musical number (“Love Can’t Afjord to wait”). Earlier this month I spent a week at the OpenStack conference. But once you realize that there are, in fact, several OpenStack conferences happening at the same time and place, it makes more sense. Vikings fight zombies.

Hardware 56

Hardware Latency Virtualization Cloud 56

VoltDB

JUNE 1, 2017

An opening scene involving a traffic jam of Viking boats and a musical number (“Love Can’t Afjord to wait”). Earlier this month I spent a week at the OpenStack conference. But once you realize that there are, in fact, several OpenStack conferences happening at the same time and place, it makes more sense. Vikings fight zombies.

Hardware 40

Hardware Latency Virtualization Cloud 40

Adrian Cockcroft

NOVEMBER 11, 2019

It would take 5–10 minutes after the problem occurred to appear as a problem, then people have to notice and respond to emails or pager text messages, dial into a conference call, and log in to monitoring dashboards before any human response can start. This is why most AWS regions have three availability zones.

Latency 52

Latency Engineering Systems Hardware 52

Adrian Cockcroft

NOVEMBER 11, 2019

It would take 5–10 minutes after the problem occurred to appear as a problem, then people have to notice and respond to emails or pager text messages, dial into a conference call, and log in to monitoring dashboards before any human response can start. This is why most AWS regions have three availability zones.

Latency 53

Latency Engineering Systems Hardware 53

Brendan Gregg

SEPTEMBER 5, 2017

It's rare to bump into a maintainer: those I know keep their heads down working on lkml and the sublists, and usually avoid blog posts, meetups, and conferences (with some exceptions, like Linux Plumbers, Kernel Summit, NetDev, and Kernel Recipes. From another tracker, for the US: Source: www.indeed.com.

Virtualization 76

Virtualization AWS Engineering Hardware 76