Remove 2010 Remove Availability Remove Benchmarking Remove Hardware
article thumbnail

Why Browsers Get Built

Alex Russell

In both cases, the OS will task the browser team to heavily prioritise integrations with the latest OS and hardware features at the expense of more broadly useful capabilities — e.g. shipping "notch" CSS and "force touch" events while neglecting Push. Examples include IE 7+ and Safari from 2010-onward.

article thumbnail

The Performance Inequality Gap, 2024

Alex Russell

This split decision was available via last year's update , but was somewhat buried. HTML, CSS, images, and fonts can all be parsed and run at near wire speeds on low-end hardware, but JavaScript is at least three times more expensive, byte-for-byte. Going forward, I'll produce both as top-line guidance. In the U.S., This nets out to 2.32

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

The Performance Inequality Gap, 2021

Alex Russell

Modern network performance and availability. Hardware Past As Performance Prologue. Using a global ASP as a benchmark can further mislead thanks to the distorting effect of ultra-high-end prices rising while shipment volumes stagnate. But the hardware future is not evenly distributed, and web workloads aren't heavily parallel.

article thumbnail

The evolution of single-core bandwidth in multicore processors

John McCalpin

Looking at sustained single-core bandwidth for a kernel composed of 100% reads, the trends for a large set of high-end AMD and Intel processors are shown in the figure below: So from 2010 to 2023, the sustainable single-core bandwidth increased by about 2x on Intel processors and about 5x on AMD processors. Details in the next blog entry.)