When it becomes reachable through WASM or browser Javascript optimization (if it isn't already), that seems like a big problem (easy DoS, probably a tricky RCX)

When it becomes reachable through WASM or browser Javascript optimization (if it isn't already), that seems like a big problem (easy DoS, probably a tricky RCX). Ideally browser vendors will hold off on that; besides this, there are the Intel throttling issues for some AVX2 instructions that could be an annoyance. But AVX2 is good for benchmarks...