Remove 2010 Remove Benchmarking Remove Hardware Remove Processing
article thumbnail

The evolution of single-core bandwidth in multicore processors

John McCalpin

This metric is interesting because we don’t always have the luxury of parallelizing every application we run, and our operating systems almost always process each call (e.g., GHz, 1530 GB/s peak BW from 6 HBM stacks), I see single-thread sustained memory bandwidth of 304 GB/s on the ReadOnly benchmark used here. Stay tuned!

article thumbnail

Why Browsers Get Built

Alex Russell

This adds powerfully to the usual moat-digger's weaponisation of consensus processes. Examples include IE 7+ and Safari from 2010-onward. native, OS-specific) platform and the hopefully weaker web platform. Apple has perfected the moat, preventing competitors from even potentially offering disruptive features.

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

Advances in browser content processing. 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. Modern network performance and availability. Content Is Dead, Long Live Content. Mind The Gap.

article thumbnail

The Performance Inequality Gap, 2024

Alex Russell

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. Meanwhile, budget segment devices have finally started to see improvement ( as this series predicted ), thanks to hand-me-down architecture and process node improvements.