Remove 2016 Remove Benchmarking Remove Cache Remove Storage
article thumbnail

The Performance Inequality Gap, 2021

Alex Russell

Back in 2016, I gave a talk outlining the causes and effects of the terrible performance of web apps built using popular tools on the fastest-growing device segment: low-end to mid-range Android phones. A then-representative $200USD device had 4-8 slow (in-order, low-cache) cores, ~2GiB of RAM, and relatively slow MLC NAND flash storage.

article thumbnail

Progress Delayed Is Progress Denied

Alex Russell

As an engineer on a browser team, I'm privy to the blow-by-blow of various performance projects, benchmark fire drills, and the ways performance marketing (deeply) impacts engineering priorities. With each team, benchmarks lost are understood as bugs. Chrome has missed several APIs for 3+ years: Storage Access API.

Media 145
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

AMD EPYC Processors in Azure Virtual Machines

SQL Performance

Back on December 5, 2017, Microsoft announced that they were using AMD EPYC 7551 processors in their storage-optimized Lv2-Series virtual machines. The L3 cache size is 64MB. I wrote about using CPU-Z to benchmark the Intel Xeon E5-2673 v3 processor in an Azure VM in this article. Figure 1: CPU-Z Benchmark Results for LS16v2.

Azure 42
article thumbnail

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

Alex Russell

Budgets are scaled to a benchmark network & device. Deciding what benchmark to use for a performance budget is crucial. Simulated packet loss and variable latency, however, can make benchmarking extremely difficult and slow. The true median device from 2016 sold at about ~$200 unlocked. Global Ground-Truth.