JetStream 3.0 Benchmark Debuts: Web Browsers Face New Performance Gauntlet with WebAssembly Overhaul

Breaking: Apple, Google, and Mozilla Release JetStream 3.0

Today, the WebKit team at Apple, alongside engineers from Google and Mozilla, announced the release of JetStream 3.0, the latest iteration of the cross-browser benchmark suite. The update marks a fundamental shift in how browser engines measure performance, especially for WebAssembly (Wasm) workloads and modern large-scale web applications.

“JetStream 3 is a refresh that reflects the evolution of the web,” said a WebKit engineering lead. “We’ve moved beyond measuring startup and runtime separately because today’s engines have made those phases nearly instantaneous.” The collaborative announcement covers the suite’s breadth, but the WebKit team shared deeper insights into the engineering behind JavaScriptCore’s improvements.

Background: Why the Update Was Urgent

Benchmarks are crucial tools for driving browser performance, but they must evolve with the web. JetStream 2, released when WebAssembly was still in its infancy, focused on large C/C++ applications that tolerated long startup times for high throughput. That era has ended.

“As engines optimized WebAssembly instantiation, we hit a paradoxical problem,” explained a Mozilla performance engineer. “Startup times fell so low that scoring broke.” In JetStream 2, sub‑1ms times were rounded to zero by JavaScript’s Date.now(), producing an infinite score. A temporary patch capped scores at 5,000, but the flaw signaled that engines had outgrown the old benchmark.

Modern WebAssembly Demands New Metrics

Today, Wasm is embedded in critical page‑load paths—powering image decoders, UI frameworks, and libraries. “A zero‑startup time in a microbenchmark doesn’t capture how Wasm is used in real‑world scenarios,” noted a Google V8 contributor. JetStream 3 replaces the two‑phase scoring with a unified approach that reflects actual workload performance.

What This Means for Browser Development

JetStream 3 introduces workloads that mirror contemporary web applications—larger, more complex, and reliant on Wasm for core functionality. Browser engines must now optimize for a broader set of patterns, not just historical benchmarks. This shift will drive innovations in just‑in‑time compilation, memory management, and concurrent execution.

“The new benchmark suite pushes us to think about performance across the entire spectrum of web technologies,” said the WebKit lead. “It’s no longer enough to optimize for a single synthetic test.”

Key Changes in JetStream 3.0

• Unified Wasm scoring – No more separate startup/runtime phases; single score reflects end‑to‑end performance.
• Larger‑scale scenarios – Tests now include multi‑megabyte codebases and complex interleaving of JavaScript and Wasm.
• Elimination of the infinite‑score bug – Updated timing logic prevents zero‑time artifacts.
• Collaborative design – Jointly developed by WebKit, V8, and SpiderMonkey teams to ensure cross‑engine relevance.

Expert Reaction

Industry analysts view JetStream 3 as a necessary correction. “Benchmarks should evolve as fast as the technology they measure,” said Dr. Elena Torres, a performance researcher at the Web Foundation. “JetStream 3 acknowledges that WebAssembly is no longer a niche feature—it’s a backbone of modern web apps.”

The update arrives as browsers race to support emerging standards like WebGPU and advanced threading. JetStream 3 provides a common yardstick that can accelerate optimization across all major engines.

Looking Ahead

The JetStream 3 repository is live on GitHub, and browser teams are already reporting score improvements. “We expect this suite to become the de facto standard for benchmarking the next generation of web platforms,” concluded the WebKit team member. Development cycles will tighten as engines compete to top the charts.

For detailed technical notes, see the WebKit blog post about JavaScriptCore’s engineering changes.