You can try increasing `N` in the nbody problem, and also measuring the memory overhead. You could also try one of the hashing / crypto algorithms in JS. They

You can try increasing `N` in the nbody problem, and also measuring the memory overhead. You could also try one of the hashing / crypto algorithms in JS. They should involve a lot of integer arithmetic that should make WebAssembly stand out. More tips: * for performance measurement, setup the benchmark so that JS run takes atleast 30 seconds. (Increase N, etc) * close all other applications and tabs * If you have linux, set the CPU governor to performance * Measure the CPU temperature and make sure you let the CPU cool down between runs. In modern CPUs, the cores get throttled automatically when they reach a certain temperature.