Remove 2017 Remove Benchmarking Remove Cache Remove Storage
article thumbnail

The Performance Inequality Gap, 2021

Alex Russell

TL;DR: A lot has changed since 2017 when we last estimated a global baseline resource per-page resource budget of 130-170KiB. A then-representative $200USD device had 4-8 slow (in-order, low-cache) cores, ~2GiB of RAM, and relatively slow MLC NAND flash storage. The Moto G4 , for example. Here begins our 2021 adventure.

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. The L3 cache size is 64MB.

Azure 42
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

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
article thumbnail

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

Alex Russell

— Alex Russell (@slightlylate) October 4, 2017. 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. Maybe "ambush by JS"?