Remove 2016 Remove Benchmarking Remove Cache Remove Database
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. All modern browsers are fast, Chromium and Safari/WebKit included. Content Indexing.

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

The L3 cache size is 64MB. Both of these Intel processors are special bespoke models that are not in the Intel ARK database. 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. The L3 cache size is 64MB.

Azure 42
article thumbnail

Is Intel Doomed in the Server CPU Space?

SQL Performance

From 2007 until 2016, Intel was able to successfully execute their Tick-Tock release strategy, where they would introduce a new processor microarchitecture roughly every two years (a Tock release). This made it easier for database professionals to make the case for a hardware upgrade, and made the typical upgrade more worthwhile.

Servers 46