Thomas Daede

Looking at AWCY results, a default constraint of tiles no smaller than 512x512 seems like a good middle ground.

It quickly becomes resolution dependent at greater tile counts: https://beta.arewecompressedyet.com/?job=4tiles-343461dcbb671b601da34b3477532fa1ef2edf83%402019-06-20T23%3A09%3A03.664Z&job=master-343461dcbb671b601da34b3477532fa1ef2edf83 I want to treat this sorta like a speed feature, e.g. for doubling encode time by going from 2->1 tiles,...

We'll happily accept WebAssembly patches (including SIMD).

Have you tried running this through AWCY?

Do you have awcy results of this rebased on the new activity masking patch?

Can you try rerunning this on master, which now uses satd for intra pruning?

It's so you can jump and look at more detailed results. I could make it optional I suppose.

I originally enforced squashing, everyone hated it so I stopped. The main issue is that CI doesn't run on each individual commit, so by not squashing we have some revs...

@lu-zero please re-review

TBH I think a better course of action is removing expensive mallocs if there are any.