I started to look at CPU overheads in MyRocks and upstream InnoDB. While I am happy to file bugs for MyRocks as they are likely to be fixed, I am not sure how much energy I want to put into proper bug reports for upstream InnoDB. So I will just write blog posts about them for now.
I created flamegraphs while running sysbench with cached databases (more likely to be CPU bound) and the problem here occurs on an 8-core PN53 where sysbench was run with 1 thread. Here I use perf record -e cycles to collect data for flamegraphs and then I focus on the percentage of samples in a given function (and its callees) as a proxy for CPU overhead.The flamegraphs are here.
The workload here is the update-nonindex microbenchmark. The throughput for a release relative to MySQL 5.6.51 is -> (QPS for $version) / (QPS for 5.6.51). The results below show that 8.0.37 gets about 62% of the QPS relative to 5.6.51.
- 0.86 in 5.7.44
- 0.79 in 8.0.11
- 0.67 in 8.0.28
- 0.62 in 8.0.37
- 32.77% in 5.6.51 from ~17% in mysql_update and ~12% from trans_commit_stmt
- 65.89% in 5.7.44 from ~39% in Sql_cmd_update::execute and ~22% from trans_commit_stmt
- 67.30% in 8.0.28 from ~38% in Sql_cmd_dml::execute and ~23% from trans_commit_stmt
- 67.97% in 8.0.37 from ~40% in Sql_cmd_dml::execute and ~21% from trans_commit_stmt
%20_%20(QPS%20for%208.0.34).png)
For comparisons, it might be more useful to use https://github.com/brendangregg/FlameGraph/blob/master/difffolded.pl
ReplyDeleteSometimes I use that but it is only useful when function names don't change much and they change a lot from 5.6 to 8.0. I have done a bit of editing in the past to fix small changes in function names when trying to use difffolded.
Delete