Remove AWS Remove Conference Remove Database Remove Traffic
article thumbnail

Weekend Reading: Amazon Aurora: Design Considerations for High Throughput Cloud-Native Relational Databases.

All Things Distributed

In many, high-throughput, OLTP style applications the database plays a crucial role to achieve scale, reliability, high-performance and cost efficiency. For a long time, these requirements were almost exclusively served by commercial, proprietary databases.

Database 117
article thumbnail

The Speed of Time

Brendan Gregg

A Cassandra database cluster had switched to Ubuntu and noticed write latency increased by over 30%. top(1) showed that only the Cassandra database was consuming CPU. 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 126
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

The Speed of Time

Brendan Gregg

A Cassandra database cluster had switched to Ubuntu and noticed write latency increased by over 30%. top(1) showed that only the Cassandra database was consuming CPU. 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 52
article thumbnail

Serverless at re:Invent 2017

The Symphonia

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.

article thumbnail

The Speed of Time

Brendan Gregg

A Cassandra database cluster had switched to Ubuntu and noticed write latency increased by over 30%. top(1) showed that only the Cassandra database was consuming CPU. 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
article thumbnail

Failure Modes and Continuous Resilience

Adrian Cockcroft

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
article thumbnail

Failure Modes and Continuous Resilience

Adrian Cockcroft

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