Remove Benchmarking Remove Network Remove Traffic Remove Transportation
article thumbnail

Building Netflix’s Distributed Tracing Infrastructure

The Netflix TechBlog

Reconstructing a streaming session was a tedious and time consuming process that involved tracing all interactions (requests) between the Netflix app, our Content Delivery Network (CDN), and backend microservices. Our trace data collection agent transports traces to Mantis job cluster via the Mantis Publish library.

article thumbnail

Can You Afford It?: Real-world Web Performance Budgets

Alex Russell

We constrain ourselves to a real-world baseline device + network configuration to measure progress. Budgets are scaled to a benchmark network & device. JavaScript is the single most expensive part of any page in ways that are a function of both network capacity and device speed. The median user is on a slow network.

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

Front-End Performance Checklist 2021

Smashing Magazine

Networking, HTTP/2, HTTP/3 OCSP stapling, EV/DV certificates, packaging, IPv6, QUIC, HTTP/3. CrUX generates an overview of performance distributions over time, with traffic collected from Google Chrome users. If you don’t have a device at hand, emulate mobile experience on desktop by testing on a throttled 3G network (e.g.

article thumbnail

Edgar: Solving Mysteries Faster with Observability

The Netflix TechBlog

Edgar captures 100% of interesting traces , as opposed to sampling a small fixed percentage of traffic. This difference has substantial technological implications, from the classification of what’s interesting to transport to cost-effective storage (keep an eye out for later Netflix Tech Blog posts addressing these topics).

Latency 296
article thumbnail

Front-End Performance Checklist 2020 [PDF, Apple Pages, MS Word]

Smashing Magazine

If you don’t have a device at hand, emulate mobile experience on desktop by testing on a throttled 3G network (e.g. To make the performance impact more visible, you could even introduce 2G Tuesdays or set up a throttled 3G/4G network in your office for faster testing. 300ms RTT, 1.6 Mbps down, 0.8