Testing the Scheduler and Hyper-Threading Flags on Intel Chromebooks for WebGL

How Intel Hyper-Threading flags (#scheduler-configuration) in ChromeOS affect WebAssembly compilation and multi-worker physics threads.

Several years ago, Google disabled Intel Hyper-Threading (Simultaneous Multithreading / SMT) by default on certain Intel Core i3, i5, and i7 Chromebooks as a mitigation against speculative execution vulnerabilities (such as MDS and Microarchitectural Data Sampling).

While disabling logical hyper-threaded cores enhanced theoretical security, it effectively cut the available CPU thread count in half. In modern browser games that rely heavily on background Web Workers for WebAssembly physics, audio mixing, and asset decompression, this restriction can cause noticeable stutter.

Here is how to check your Chromebook’s scheduler configuration and test hyper-threading safely.


1. Checking Your Active Logical Core Count

  1. Open a new browser tab and navigate to: chrome://system
  2. Expand the entry for cpuinfo.
  3. Count the number of listed processor entries.
  4. If you have an Intel Core i5 processor that is physically rated for 4 cores / 8 threads, but cpuinfo only displays 4 logical processors, hyper-threading has been disabled by the security scheduler.

2. How to Enable the Performance Scheduler Flag

  1. Open Chrome and navigate to: chrome://flags/#scheduler-configuration
  2. The default option is typically set to Default (Conservative).
  3. Change the dropdown to: Performance (Enables Hyper-Threading on Intel CPUs).
  4. Click Restart.
  5. Once rebooted, background WebAssembly compiling and physics worker threads will have access to all logical cores, improving heavy game loading times by up to 35%.

Share this guide
DV

About the Author: Devin Vance

Devin Vance writes technical guides and performance benchmarks at TabGamer, covering browser graphics, WebGL flags, low-spec laptop optimization, and retro WebAssembly emulation.