Fixed MobX benchmark after upgrading by swapping minifier and enabling batching

[mweststrate]

This fixes: mobxjs/mobx-react#877

React became really slow after upgrading to 16.6+, which is caused by a bug in the default webpack minifier (facebook/react#13987). This might apply to other React based frameworks as well.

Also enabled ReactDOM batching support according to best practice.

[krausest]

Thanks. Results are updated. I hoped to see a clear improvement in comparison to the old results, but sadly results didn't change much. (System was rebooted before runnning and I'm always running keyed/vanillajs as a check and its results look fine)
How much of an improvement did you expect?

[mweststrate]

I'd expect them to be roughly the same indeed. We didn't make much performance improvements that would show up in this benchmark. MobX is kinda optimized for fine grained updates to widely shared state and when complicated derived data comes into play. But that is not the case in this benchmark :)

…

On Thu, Jun 25, 2020 at 8:21 PM Stefan Krause ***@***.***> wrote: Thanks. Results <https://krausest.github.io/js-framework-benchmark/current.html> are updated. I hoped to see a clear improvement in comparison to the old <https://krausest.github.io/js-framework-benchmark/2020/table_chrome_83.0.4103.106.html> results, but sadly results didn't change much. (System was rebooted before runnning and I'm always running keyed/vanillajs as a check and its results look fine) How much of an improvement did you expect? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#752 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAN4NBA6WRDWZJY4V56YWDDRYOPTHANCNFSM4OCUMJRQ> .