It seems odd, though. I guess it's all PostgreSQL all the time for me, from now on.
Even their own benchmarks show MySQL 5.7 dipping below previous versions at the low end of the concurrency scale.
I also showed the impact for IO-bound workloads, and even there the regression is larger than I want. But not as bad as the in-memory workloads.
Those blindly suggesting MariaDB or Percona is all well and good but naive. Percona generally follows MySQL upstream but makes their own little tweaks which could be (but are not always) fixed in MySQL upstream based on differing specific priorities.
MariaDB is highly diverged at this point and likely has a whole different set of problems and benefits.
Author of these posts is well known for a long (10+ years) history of working with MySQL at a deep level rivalling that of many of the developers, generally writes good stuff (though is not infallible :)
If you're not using MySQL in the first place, why would you care?
However, for MySQL in an existing application, the migration costs might make it not worth it. There can be a number of pernicious gotchas that aren't obvious at first. MariaDB is more or less set-and-forget.