這篇文章主要介紹MySQL 5.7 vs 8.0版本的性能有什么區(qū)別,文中介紹的非常詳細,具有一定的參考價值,感興趣的小伙伴們一定要看完!
網(wǎng)站建設哪家好,找創(chuàng)新互聯(lián)公司!專注于網(wǎng)頁設計、網(wǎng)站建設、微信開發(fā)、微信小程序定制開發(fā)、集團企業(yè)網(wǎng)站建設等服務項目。為回饋新老客戶創(chuàng)新互聯(lián)還提供了望都免費建站歡迎大家使用!
測試mysql5.7和mysql8.0 分別在讀寫、只讀、只寫模式下不同并發(fā)時的性能(tps,qps)
機器
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模式(高性能)下進行

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)

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<<EOF
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以上是MySQL 5.7 vs 8.0版本的性能有什么區(qū)別的所有內(nèi)容,感謝各位的閱讀!希望分享的內(nèi)容對大家有幫助,更多相關知識,歡迎關注創(chuàng)新互聯(lián)行業(yè)資訊頻道!
網(wǎng)站題目:MySQL5.7vs8.0版本的性能有什么區(qū)別
瀏覽地址:http://www.chinadenli.net/article0/gpcioo.html
成都網(wǎng)站建設公司_創(chuàng)新互聯(lián),為您提供虛擬主機、外貿(mào)網(wǎng)站建設、軟件開發(fā)、微信小程序、小程序開發(fā)、網(wǎng)站內(nèi)鏈
聲明:本網(wǎng)站發(fā)布的內(nèi)容(圖片、視頻和文字)以用戶投稿、用戶轉(zhuǎn)載內(nèi)容為主,如果涉及侵權(quán)請盡快告知,我們將會在第一時間刪除。文章觀點不代表本網(wǎng)站立場,如需處理請聯(lián)系客服。電話:028-86922220;郵箱:631063699@qq.com。內(nèi)容未經(jīng)允許不得轉(zhuǎn)載,或轉(zhuǎn)載時需注明來源: 創(chuàng)新互聯(lián)