Making Workers Work For You
summary
Practical guide to using browser workers with measured tradeoffs and gotchas: dynamic creation via blob URLs works cross-origin, but transferable objects are inconsistently implemented (IE10/11 broken), so Blob transfers can be fastest because they pass pointers. Benchmarks show 1000 round-trip transfers from ~50ms to 400ms depending on type and browser, nested objects and Float64 arrays are slow, Firefox treats ArrayBuffer poorly, memory costs ≈250–1000KB per worker, best performance when workers ≈ CPU cores, XHR in workers loses main-thread cache.
AI-written summary · about
chapters (4)
- 0:00Start
- 13:09RE-USE WORKERS COST FOR CREATING & DESTROYING WORKERS
- 14:13XHR PROXY SEND URL TO WORKER WORKER DOES XHR WORKER SENDS RESPONSE TO MAIN THREAD
- 19:42WORKER MGMT / MARSHALLING
related talks
23mMaking Workers Work For You
22mFearless Concurrency with JavaScript and Beyond
15mWeb Workers — Add Productivity to Your Web Applications
24mWeaving Webs of Workers
25mDemystifying Web Workers and Service Workers
13mHow to Use Web Workers for Fun and Profit
23mMultithreading in Javascript
24mWeb Workers - Little Minions At Work for Optimizing Performance