It would be interesting to do this same comparison with MariaDB.<p>I wonder if that project has managed to continue progressing while MySql seems to have regressed.<p>It's super easy for all of us on HN to say "Oh look Oracle ruined another thing". But it would much more interesting to have quantified results to compare from.
Hmmm, consistently deteriorating performance over time is rather suspicious. A move by Oracle to kill off competition for their implementations? I can only speculate, though.<p>It seems odd, though. I guess it's all PostgreSQL all the time for me, from now on.
tldr: mysql is getting worse for small, in memory workloads with low concurrency.<p>for the average medium to high traffic mysql install, i find 5.7 to be much faster than 5.6 or mariadb where concurrency and varying workloads prevail.<p>ymmv, do your own testing to see which db is a good platform for your specific workload. maybe it's mysql 5.6 maybe it's mariadb, maybe it's postgres.<p>for me mysql 5.7 brings much awaited niceness, saner defaults and even though not all workloads are better on it i think oracle is really trying to iterate. likely they will fix this regression and there would be little reason to use it over 5.6 or older.
Would Oracle slowly degrade performance so they could sling their enterprise offerings better.... hmm. However, this is just going to kill MySQL altogether rather than actually achieve its implied goal. I guess you could say, competition always finds a way.