article thumbnail

Improving our video encodes for legacy devices

The Netflix TechBlog

we announced our intention to stream video over 13 years ago, in January 2007?—?and This multi-pass strategy , previously employed for our mobile encodes , allows us to avoid over-allocating bits to less complex content, as compared to using a complexity-defined, albeit fixed, bitrate for the entire title.

article thumbnail

A Decade of Dynamo: Powering the next wave of high-performance, internet-scale applications

All Things Distributed

The success of our early results with the Dynamo database encouraged us to write Amazon's Dynamo whitepaper and share it at the 2007 ACM Symposium on Operating Systems Principles (SOSP conference), so that others in the industry could benefit. This was the genesis of the Amazon Dynamo database.

Internet 130
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

Egnyte Architecture: Lessons learned in building and scaling a multi petabyte content platform

High Scalability

Egnyte is a secure Content Collaboration and Data Governance platform, founded in 2007 when Google drive wasn't born and AWS S3 was cost-prohibitive. Edge caching. In general, Egnyte connect architecture shards and caches data at different levels based on: Amount of data. Nginx for disk based caching. Hybrid Sync.

article thumbnail

Is Intel Doomed in the Server CPU Space?

SQL Performance

From 2007 until 2016, Intel was able to successfully execute their Tick-Tock release strategy, where they would introduce a new processor microarchitecture roughly every two years (a Tock release). They will also have up to 256MB of L3 cache per processor. So, what has changed my mind? The Death of Tick-Tock.

Servers 46
article thumbnail

The Best In Performance Interview Series – Episode #4: Recap with Rich Howard

Rigor

When working on a project for the Man Booker Prize in 2007 (now known as the Booker Prize), Howard saw first-hand how a heavy-load day could impact a website. Make technical changes like increasing the length of cache headers within their particular assets. Retrospectives. Lessons learned.