I'm glad V8 (and Chrome) are getting streaming compilation for WASM. That was an annoying pain point I saw when playing with it (fat binaries meant a long downl

I'm glad V8 (and Chrome) are getting streaming compilation for WASM. That was an annoying pain point I saw when playing with it (fat binaries meant a long download and compile time, almost penalizing you 2 times for every byte). However I noticed that Firefox's recent update with their streaming and tiered WASM compiler is still almost a magnitude faster (using the benchmark at [0] it takes 717ms in Firefox 58, and 4283ms in Chrome 66 on my machine with a good gigabit connection and an i7 4930k) I tend to think of my PC as fairly "high end" (yeah, it's a few years old, but still is a powerhouse in my opinion!) but I'm just not seeing the speeds that they are talking about in the blog post. Is the difference really just in Firefox's 2-tiered compiler!? I noticed that the benchmarks are in seconds (!) of compile time, does this streaming compiler only really shine with much larger WASM modules? Or is that benchmark not a good representation of a general workload (it was made by a Mozilla employee, for what it's worth). [0] https://lukewagner.github.io/test-tanks-compile-time/ https://lukewagner.github.io/test-tanks-compile-time/