Making Workers Work For You
summary
Benchmarks show transferable objects behave inconsistently: Chrome/Safari move big binary quickly, Firefox treats ArrayBuffer much slower, and IE10/11 misimplement the transfer API; passing a large Float64Array can be slower than shipping a Blob URI because blobs act like pointers. Memory costs are roughly 250–1000KB per worker and Chrome/Safari cap out around 250–500 workers; peak throughput occurs when worker count matches CPU cores. XHR from workers misses main-thread cache, and reusing workers is generally faster than repeatedly creating them.
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
