Remove 2007 Remove Cache Remove Performance Remove Strategy
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

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

Rigor

Reading time 8 min Rigor’s “The Best in Performance” interview series offers the chance to listen in on conversations with web performance industry experts, thought leaders, and technologists as they discuss current trends, challenges, and lessons that impact the performance and APM space today. Retrospectives.

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

For many years, I explicitly advised people not to run their SQL Server workloads on AMD hardware because of the much lower single-threaded CPU performance and consequently higher SQL Server core license costs. This has led to a very noticeable reduction in generational performance increases since Broadwell-EP, as shown in Figure 1.

Servers 46
article thumbnail

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

All Things Distributed

We were pushing the limits of what was a leading commercial database at the time and were unable to sustain the availability, scalability and performance needs that our growing Amazon business demanded. Performant – The service would need to be able to maintain consistent performance in the face of diverse customer workloads.

Internet 128