Remove 2006 Remove Architecture Remove Cloud Remove Virtualization
article thumbnail

AWS EC2 Virtualization 2017: Introducing Nitro

Brendan Gregg

Hardware virtualization for cloud computing has come a long way, improving performance using technologies such as VT-x, SR-IOV, VT-d, NVMe, and APICv. At Netflix, we've been using these technologies as they've been made available for instance types in the AWS EC2 cloud. Each dimension has progressed through these stages: 1.

article thumbnail

AWS EC2 Virtualization 2017: Introducing Nitro

Brendan Gregg

Hardware virtualization for cloud computing has come a long way, improving performance using technologies such as VT-x, SR-IOV, VT-d, NVMe, and APICv. At Netflix, we've been using these technologies as they've been made available for instance types in the AWS EC2 cloud. Each dimension has progressed through these stages: 1.

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

Proposal for a Realtime Carbon Footprint Standard

Adrian Cockcroft

The challenge is that accurate data isn’t available immediately, and cloud providers currently only provide monthly carbon data, with several months lag. Cloud providers don’t disclose their own REC and Private Purchase Agreements, but these are taken into account in their monthly reports, with a few months delay.

Energy 52
article thumbnail

Looking back at 10 years of compartmentalization at AWS

All Things Distributed

But every year when March 14th comes around, it's a good reminder that Amazon S3 originally launched on Pi Day, March 14, 2006. A concept that has changed infrastructure architecture is now at the core of both AWS and customer reliability and operations. The Amazon S3 team still celebrate with homemade pies!

AWS 132
article thumbnail

10 Lessons from 10 Years of Amazon Web Services

All Things Distributed

The epoch of AWS is the launch of Amazon S3 on March 14, 2006, now almost 10 years ago. The expectation was that with each order or two of magnitude, we would need to revisit and revise the architecture to make sure we could address the issues of scale.

AWS 144