MySQL 5.7 vs 8.0，哪個性能更牛？

作者：jiaxin
出處：http://www.cnblogs.com/YangJiaXin/

背景

測試mysql5.7和mysql8.0 分別在讀寫、只讀、只寫模式下不同并發(fā)時的性能（tps，qps）

前提

• 測試使用版本為mysql5.7.22和mysql8.0.15

• sysbench測試前先重啟mysql服務，并清空os的cache（避免多次測試時命中緩存）

• 每次進行測試都是新生成測試數(shù)據(jù)后再進行mysql5.7和mysql8.0的測試

• 每次測試時保證mysql5.7和mysql8.0的配置參數(shù)一致

環(huán)境

機器

cat?/etc/redhat-release?|?xargs?echo?'版本?'?&&?dmidecode?-s?system-product-name?|?xargs?echo?'是否虛擬化?'?&&?cat?/proc/cpuinfo?|grep?"processor"|wc?-l?|?xargs?echo?'cpu核數(shù)?'?
版本?CentOS?Linux?release?7.5.1804?(Core)??
是否虛擬化?KVM??
cpu核數(shù)?4

myql5.7.22

5.7.22-log
innodb_buffer_pool_size?128M
innodb_log_buffer_size??64M
innodb_log_file_size????48M
binlog_format???ROW
log_bin?ON
transaction_isolation???REPEATABLE-READ

mysql8.0.15

8.0.15
innodb_buffer_pool_size?128M
innodb_log_buffer_size??64M
innodb_log_file_size????48M
binlog_format???ROW
log_bin?ON
transaction_isolation???REPEATABLE-READ

sysbench

sysbench?-V
sysbench?1.1.0?(using?bundled?LuaJIT?2.1.0-beta3)

測試

• 在不同的持久化策略下（binlog, redo log持久化）mysql5.7和mysql8.0 在讀寫模式、只讀模式、只寫模式（oltp_read_write，oltp_read_only，oltp_write_only）下的性能表現(xiàn)

• sysbench 測試時間為60s，測試的表數(shù)量為20

• 測試分別在雙1模式（安全性）和0 2模式（高性能）下進行

雙1模式下

SHOW?GLOBAL??VARIABLES?WHERE?Variable_name?IN('sync_binlog','innodb_flush_log_at_trx_commit');
+--------------------------------+-------+
|?Variable_name??????????????????|?Value?|
+--------------------------------+-------+
|?innodb_flush_log_at_trx_commit?|?1?????|
|?sync_binlog????????????????????|?1???|
+--------------------------------+-------+

mysql5.7和mysql8.0 在讀寫模式下的表現(xiàn)

mysql5.7和mysql8.0 在只讀模式下的表現(xiàn)

mysql5.7和mysql8.0 在只寫模式下的表現(xiàn)

0 2 模式下

SHOW?GLOBAL??VARIABLES?WHERE?Variable_name?IN('sync_binlog','innodb_flush_log_at_trx_commit');
+--------------------------------+-------+
|?Variable_name??????????????????|?Value?|
+--------------------------------+-------+
|?innodb_flush_log_at_trx_commit?|?2?????|
|?sync_binlog????????????????????|?0???|
+--------------------------------+-------+

mysql5.7和mysql8.0 在讀寫模式下的表現(xiàn)

mysql5.7和mysql8.0 在只讀模式下的表現(xiàn)

mysql5.7和mysql8.0 在只寫模式下的表現(xiàn)

• 0 2 配置，只寫模式下，mysql5.7.22的tps 抖動比較大；mysql5.7.22 的qps比mysql8.0.15好1/3左右

結論

• 整體來看，mysql5.7.22在讀寫模式、只讀模式、只寫模式下的表現(xiàn)是優(yōu)于mysql8.0.15的

• 隨著并行數(shù)的增加，性能表現(xiàn)不會也跟著增加，還會出現(xiàn)下降

• 本次測試結果是在配置很低的情況下進行的，不代表絕對

注意
sysbench 需要設置--db-ps-mode=disable 禁用預編譯語句，不然并發(fā)測試線程多時會報下面的錯誤

FATAL:?mysql_stmt_prepare()?failed
FATAL:?MySQL?error:?1461?"Can't?create?more?than?max_prepared_stmt_count?statements?(current?value:?16382)"
FATAL:?mysql_stmt_prepare()?failed
FATAL:?MySQL?error:?1461?"Can't?create?more?than?max_prepared_stmt_count?statements?(current?value:?16382)"
FATAL:?thread_init'?function?failed:?/usr/local/share/sysbench/oltp_common.lua:288:?SQL?API?error?FATAL:?mysql_stmt_prepare()?failed?FATAL:?MySQL?error:?1461?"Can't?create?more?than?max_prepared_stmt_count?statements?(current?value:?16382)"?FATAL:thread_init'?function?failed:?/usr/local/share/sysbench/oltp_common.lua:288:?SQL?API?error
FATAL:?mysql_stmt_prepare()?failed

使用腳本

cat?sysbench_test_mysql5.7_8.0_tps_qps.sh
#!/bin/bash
#用于sysbench?測試在讀寫模式、只讀模式、只寫模式下?mysql5.7和mysql8.0?的tps,qps
#nohup?bash?$0?>/tmp/sysbench_test?2>&?1?&
#

user=admin
passwd=admin
ports="8015?57222"
host=127.0.0.1
sysbench_test_mode="oltp_read_write?oltp_read_only?oltp_write_only"
sysbench_test_info_path=/tmp/sysbench-test

function?red_echo?()?{

????????local?what="$*"
????????echo?-e?"$(date?+%F-%T)?\e[1;31m?${what}?\e[0m"
}

function?check_las_comm(){
????if?[?$1?-ne?0?];then
????????red_echo?$2
????????exit?1
????fi
}

function??restart_mysqld(){
??service?mysqld${1}?restart
??sleep?2
}

function??purge_binlog(){
port=$1
mysql?-u$user?-p$passwd?-P$port?-h$host<purge?binary?logs?before?now();
EOF
}


function?clean_os_cache(){
??echo?3?>?/proc/sys/vm/drop_caches
}

function??sysbench_with_diff_thread(){


thread_num=$1
port=$2
order=$3
test_mode=$4
sysbench?/usr/local/share/sysbench/${test_mode}.lua?--mysql_storage_engine=innodb??--table-size=100000?--tables=20?--mysql-db=test_1?--mysql-user=$user?--mysql-password=$passwd?--mysql-port=$port??--mysql-host=$host?--threads=$thread_num??--time=60?--report-interval=2?--db-ps-mode=disable?--events=0?--db-driver=mysql?$order

}

function??main(){
for?test_mode?in?$sysbench_test_mode;do

??for?port?in?$ports;do
????for?thread_num?in?{5,10,20,30,40,80,120,200};do
??????restart_mysqld?"$port"
??????check_las_comm??"$?"?"restart?mysqld${port}?failed?"
??????clean_os_cache
??????purge_binlog?"$port"

??????red_echo?"sysbench?$thread_num??threads?cleanup?mysqld${port}"
??????sysbench_with_diff_thread?"$thread_num"?"$port"?"cleanup"?"$test_mode">/dev/null

??????red_echo?"sysbench?$thread_num??threads?prepare?mysqld${port}"
??????sysbench_with_diff_thread?"$thread_num"?"$port"?"prepare"?"$test_mode">/dev/null

??????mkdir?-p?$sysbench_test_info_path
??????red_echo?"sysbench?$thread_num??threads?run?mysqld${port}?$test_mode"
??????sysbench_with_diff_thread?"$thread_num"?"$port"?"run"?"$test_mode"?>?$sysbench_test_info_path/${test_mode}_${thread_num}_$port

??????#?service?mysqld{port}?stop
????done
??done
done

}

main