Rigor

JULY 2, 2019

Time spent on redirect is most noticeable on mobile devices, especially since they tend to use slower networks. By adding the need for additional JavaScript resources to your page, you increase the latency caused by the need to first download the webpage and then parse and execute the JavaScript before the browser can execute the redirect.

Mobile 60

Mobile Traffic Google Latency 60

Alex Russell

DECEMBER 18, 2022

TL;DR : To serve users at the 75 th percentile ( P75 ) of devices and networks, we can now afford ~150KiB of HTML/CSS/fonts and ~300-350KiB of JavaScript (gzipped). This is a slight improvement on last year's budgets , thanks to device and network improvements. This is an ethical crisis for the frontend. 2023 Content Targets #.

Performance 113

Performance Network Mobile Latency 113

CSS Wizardry

MARCH 3, 2019

The best request is the one that never happens: in the fight for fast websites, avoiding the network is far better than hitting the network at all. Any asset that carries the no-store directive will always hit the network, no matter what. We can completely cut out the overhead of a roundtrip of latency.

Cache 264

Cache Latency Strategy Servers 264

CSS - Tricks

APRIL 1, 2021

Speed is also something Google considers when ranking your website placement on mobile. With all of this in mind, I thought improving the speed of my own version of a slow site would be a fun exercise. Using a network request inspector, I’m going to see if there’s anything we can remove via the Network panel in DevTools.

Cache 92

Cache Social Media Media Website 92

SQL Server According to Bob

SEPTEMBER 26, 2016

Performance issues surrounding Availability Groups typically were related to disk I/O or network speeds. Our customers who deployed Availability Groups were now using servers for primary and secondary replicas with 12+ core sockets and flash storage SSD arrays providing microsecond to low millisecond latencies.

Availability 40

Availability Servers Hardware Benchmarking 40

Alex Russell

MARCH 6, 2021

Thanks to progress in networks and browsers (but not devices), a more generous global budget cap has emerged for sites constructed the "modern" way: ~100KiB of HTML/CSS/fonts and ~300-350KiB of JS (compressed) is the new rule-of-thumb limit for at least the next year or two. Modern network performance and availability.

Performance 124

Performance Network Cache Metrics 124

Alex Russell

MAY 9, 2022

This is a complex topic, but to borrow from a recent post , web performance expands access to information and services by reducing latency and variance across interactions in a session, with a particular focus on the tail of the distribution (P75+). Consistent performance matters just as much as low average latency.

Performance 86

Performance Latency Metrics Engineering 86

All Things Distributed

DECEMBER 12, 2018

They can run applications in Sweden, serve end users across the Nordics with lower latency, and leverage advanced technologies such as containers, serverless computing, and more. We launched Edge Network locations in Denmark, Finland, Norway, and Sweden. Our AWS Europe (Stockholm) Region is open for business now.

AWS 124

AWS Cloud Games Serverless 124

Alex Russell

OCTOBER 22, 2017

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.

Performance 68

Performance Benchmarking Network Mobile 68

Brendan Gregg

SEPTEMBER 5, 2017

LTS (April 2016). I wrote about it in a previous post, [DTrace for Linux 2016]. Here's some output from my zfsdist tool, in bcc/BPF, which measures ZFS latency as a histogram on Linux: # zfsdist. Tracing ZFS operation latency. The hardest part on Linux is now done: kernel support. Hit Ctrl-C to end. ^C

Virtualization 76

Virtualization AWS Engineering Hardware 76

John McCalpin

NOVEMBER 5, 2016

In the latest (October 2016) revision of Intel’s Instruction Extensions Programming Reference , Intel has disclosed a fairly dramatic departure from these “traditional” approaches. With 2 FMA units that have 5-cycle latency, the code must implement at least 2*5=10 independent accumulators in order to avoid stalls.

Cache 40

Cache C++ Latency Hardware 40