Monday, August 28, 2017

Sysbench, a large server and fast SSD vs MyRocks, InnoDB and TokuDB: part 2

This provide more data using the setup in my previous post. The difference is that the previous post used 8 tables with 100M rows/table and this post uses 1 table with 800M rows/table, so this test has more opportunity for contention.

tl;dr
  • Results here are mostly similar to results from the previous test but ...
  • MyRocks does better here relative to other engines, so it suffers less from contention.
  • InnoDB and TokuDB don't do as well on this test as on the previous test so they suffer more from contention.

Results without pictures

All of the data is here. The data below is the QPS ratio comparing the QPS for MyRocks, InnoDB 5.7.17 and TokuDB 5.7.17 with InnoDB 5.6.35. A value less than one means the QPS for the engine is less than for InnoDB 5.6.35.

QPS ratio:
* rocks = myrocks.none / inno5635
* inno = inno5717 / inno5635
* toku = toku5717.none / inno5635
1 connection
rocks   inno    toku    engine/test
1.765   1.306   0.995   update-index
1.049   1.122   0.421   update-nonindex
0.842   1.020   0.351   update-nonindex-special
4.415   1.821   1.111   delete-only
0.988   1.166   0.329   read-write.range100
1.189   1.300   1.339   read-write.range10000
0.910   1.092   0.358   read-only.range100
0.980   0.966   1.246   read-only.range10000
0.862   0.950   0.257   point-query
0.949   0.949   0.271   random-points
0.515   0.885   0.606   hot-points
0.963   0.991   0.324   insert-only

8 connections
rocks   inno    toku    engine/test
5.958   2.644   2.782   update-index
1.513   1.434   0.473   update-nonindex
1.289   1.422   0.365   update-nonindex-special
1.542   0.995   0.275   delete-only
1.206   1.306   0.253   read-write.range100
1.002   1.288   1.159   read-write.range10000
1.017   1.083   0.329   read-only.range100
0.871   1.069   1.191   read-only.range10000
0.862   0.855   0.204   point-query
0.915   0.859   0.208   random-points
0.890   1.194   0.758   hot-points
0.951   1.149   0.353   insert-only

48 connections
rocks   inno    toku    engine/test
3.836   2.340   1.492   update-index
2.425   2.520   0.312   update-nonindex
2.112   2.981   0.557   update-nonindex-special
3.028   1.950   0.306   delete-only
1.790   1.643   0.122   read-write.range100
1.488   1.883   0.768   read-write.range10000
0.820   1.005   0.093   read-only.range100
0.903   1.219   0.579   read-only.range10000
0.854   0.971   0.079   point-query
0.871   0.953   0.096   random-points
0.739   1.286   0.698   hot-points
1.768   1.579   0.491   insert-only

Results with pictures

Sorry, no charts this time. Charts from the previous post are close enough.

No comments:

Post a Comment

Fixing some of the InnoDB scan perf regressions in a MySQL fork

I recently learned of Advanced MySQL , a MySQL fork, and ran my sysbench benchmarks for it. It fixed some, but not all, of the regressions f...