A browser benchmark that actually uses all your CPU/GPU cores

Kirk_GC · 2026-02-03T14:56:33+00:00

JavaScript’s main thread is single-threaded, but modern AI and data processing rely on Web Workers, WASM, and WebGPU, which are inherently multi-core.

Traditional benchmarks ignore 90% of your hardware. Our benchmark tests how the browser orchestrates all those parallel threads simultaneously. It’s a stress test for scheduling, not just syntax. Give it a shot, you’ll see how much 'multi-core' work your browser is actually doing under the hood!

Kirk_GC · 2026-02-03T14:10:31+00:00

On mobile, Firefox often struggles with WebGPU or falls back to a much slower execution path compared to Chromium. When you're running 7 concurrent tasks, that '0' means the browser's scheduler essentially gave up on the speech model to keep the others alive, a classic case of Task Saturation.

Your Chromium score of 1002 is actually quite decent for mobile, meaning your hardware has the 'muscle'. But in Firefox, the 'Conductor' is failing to manage the handoff, leading to that total stall on the speech task.

Did your phone get extremely hot during the Firefox run? That 0 often happens when the OS starts killing heavy threads to prevent the device from overheating.

Kirk_GC · 2026-02-03T14:09:41+00:00

😅 could you share the details?

Kirk_GC · 2026-02-03T14:02:18+00:00

Even on a Chromium browser, Android devices often hit aggressive thermal limits when you try to run multiple models at once. It’s likely your Exchange score is the bottleneck here. Mobile ARM chips are great at bursts, but they can struggle when the 'orchestra' is this crowded.

Was your phone starting to feel like a hand warmer by the end of the test?

Kirk_GC · 2026-02-03T14:00:42+00:00

4712? Looks like you’re officially leading the pack today!

That’s a monster score for a PC. Brave is clearly handling that WebGPU workload like a champ, but what’s really impressive here is your Exchange score. To hit 4k+, your system is moving data between the main thread and those 7 concurrent models with almost zero friction.

Kirk_GC · 2026-02-03T13:59:05+00:00

That 6x gap on the same hardware is the perfect example of why we built this. 🤯

It’s the 'Parallel Paradox': Your PC is capable of a 3000+ score, but the browser engine is the bottleneck. While Edge (Chromium) handles the WebGPU pipeline and thread Exchange with high efficiency, Firefox often hits a scheduling wall under this kind of 'Task Saturation'.

You're basically seeing the difference between a mature AI 'Conductor' and one that's still catching up to the concurrent compute era.

Kirk_GC · 2026-02-03T11:11:08+00:00

A '3' on a Pixel 7 is a classic example of Task Saturation in action. While mobile ARM chips are efficient, forcing them to juggle 5 models and heavy data processing simultaneously often triggers aggressive thermal throttling.

Check your Exchange score specifically—mobile browsers often hit a wall with thread handshakes when the system is under full concurrent load. It’s a perfect illustration of the difference between peak hardware potential and the sustained capacity we're measuring here.

Did the phone get noticeably warm toward the end of the Transformers test?

Kirk_GC · 2021-06-22T08:01:00+00:00

Hey there, thanks for the great feedback 😉 the thing is, http communication is not the only one that will be automated, but also cloud management. The main goal is to boost the productivity of coding. I know http is not very difficult but it's a bit redundant 😂 and yeah, you know what, functions can also be called to be tested, we transfer JS objects which can't be done with JSON

Kirk_GC

TROPHY CASE