Remove 2008 Remove Code Remove Latency
article thumbnail

Performance Hero: Annie Sullivan

Speed Curve

Then in 2008, Google issued a code yellow for application speed, and I was the code yellow lead for Google Docs. A critical part of the code yellow was ensuring Google's sites would be fast for users across the globe, even if they had slow networks and low end devices. How do we slice and dice them to find problem areas?

article thumbnail

DevOps automation: From event-driven automation to answer-driven automation [with causal AI]

Dynatrace

The evolution of DevOps automation Since the concept of DevOps emerged around 2007 and 2008 in response to pain points with Agile development, DevOps automation has been continuously evolving. For example, consider an e-commerce website that automatically sends personalized discount codes to customers who abandon their shopping carts.

DevOps 246
Insiders

Sign Up for our Newsletter

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

article thumbnail

Zero Configuration Service Mesh with On-Demand Cluster Discovery

The Netflix TechBlog

A brief history of IPC at Netflix Netflix was early to the cloud, particularly for large-scale companies: we began the migration in 2008, and by 2010, Netflix streaming was fully run on AWS. There is a downside to fetching this data on-demand: this adds latency to the first request to a cluster.

Traffic 229
article thumbnail

Jamstack CMS: The Past, The Present and The Future

Smashing Magazine

However, unlike the early days of the web, static sites are no longer limited to developers working in a code editor. Piecing together a website using a WYSIWYG editor and seeing the code it generated was a fascinating and educational experience that sparked an initial interest in web design. Editing a blog post in MovableType 2.0

Ecommerce 142
article thumbnail

The Surprising Effectiveness of Non-Overlapping, Sensitivity-Based Performance Models

John McCalpin

The presentation discusses a family of simple performance models that I developed over the last 20 years — originally in support of processor and system design at SGI (1996-1999), IBM (1999-2005), and AMD (2006-2008), but more recently in support of system procurements at The Texas Advanced Computing Center (TACC) (2009-present).

article thumbnail

Tuning SQL Server Reporting Services

SQL Performance

SSRS 2008 brought that component into the reporting service module. Disk latency for ReportServer and ReportServerTempDB are very important. To tune for a slow report, that usually means you need to create indexes for that specific report or tune the code within the report. Reporting Services Infrastructure.

Tuning 67
article thumbnail

The Surprising Effectiveness of Non-Overlapping, Sensitivity-Based Performance Models

John McCalpin

The presentation discusses a family of simple performance models that I developed over the last 20 years — originally in support of processor and system design at SGI (1996-1999), IBM (1999-2005), and AMD (2006-2008), but more recently in support of system procurements at The Texas Advanced Computing Center (TACC) (2009-present).