mysql tutorial column introduces the performance comparison between MySQL 5.7 and MySQL 8.0.
Background
Test the performance of mysql5.7 and mysql8.0 in different concurrency conditions in read-write, read-only, and write-only modes. (tps, qps)
Prerequisite
- The test version is mysql5.7.22 and mysql8.0.15
- Restart the mysql service before sysbench test, and clear the os cache (to avoid hitting the cache during multiple tests)
- Every time a test is performed, new test data is generated before testing mysql5.7 and mysql8.0
- Guarantee mysql5 during each test .7 The configuration parameters are consistent with mysql8.0
Environment
Machine
cat /etc/redhat-release | xargs echo '版本 ' && dmidecode -s system-product-name | xargs echo '是否虚拟化 ' && cat /proc/cpuinfo |grep "processor"|wc -l | xargs echo 'cpu核数 ' 版本 CentOS Linux release 7.5.1804 (Core) 是否虚拟化 KVM cpu核数 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)复制代码
Test
Under different persistence strategies (binlog, redo log persistence) mysql5.7 and mysql8.0 are reading and writing Performance in mode, read-only mode, write-only mode (oltp_read_write, oltp_read_only, oltp_write_only)
sysbench test time is 60s, and the number of tables tested is 20
The tests were conducted in double 1 mode (security) and 0 2 mode (high performance) respectively
-
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 | ------------------------ -------
Performance of mysql5.7 and mysql8.0 in read-write mode
- Double 1 configuration, in read-write mode, mysql5.7.22 and mysql8 .0.15 tps and qps have similar performance. When mysql8.0.15 has 120 threads concurrently, the performance drops and jitters:
Performance of mysql5.7 and mysql8.0 in read-only mode
- Double 1 configuration, in read-only mode, the tps and qps of mysql5.7.22 are about 1/3 better than mysql8.0.15; after the number of concurrent threads increases, the tps , qps did not increase, but showed a downward trend.
Performance of mysql5.7 and mysql8.0 in write-only mode
- ##Double 1 configuration, write-only In mode, as the number of concurrency increases, the performance of mysql5.7.22 is about 1/4 better than that of mysql8.0.15.
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 | +--------------------------------+-------+复制代码Performance of mysql5.7 and mysql8.0 in read-write mode
- 0 2 configuration, in read-write mode, when the number of concurrency is low, the performance of mysql5.7.22 is better than that of mysql8.0.15; when the number of concurrency is relatively high, the performance of mysql8.0.15 is better than that of mysql5.7.22; in the concurrency of 80 threads Above that, performance begins to degrade.
- 0 2配置,只读模式下,mysql5.7.22性能比mysql8.0.15 好1/3左右;随着并发数的上升,性能也没有上升,反而有下降的趋势.
mysql5.7和mysql8.0 在只写模式下的表现
- 0 2 配置,只写模式下,mysql5.7.22的tps 抖动比较大;mysql5.7.22 的qps比mysql8.0.15好1/3左右
结论
- 整体来看,mysql5.7.22在读写模式、只读模式、只写模式下的表现是优于mysql8.0.15的
- 随着并行数的增加,性能表现不会也跟着增加,还会出现下降
- 本次测试结果是在配置很低的情况下进行的,不代表绝对
注意
sysbench 需要设置--db-ps-mode=disable 禁用预编译语句,不然并发测试线程多时会报下面的错误
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 /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教程(视频)
The above is the detailed content of MySQL 5.7 vs 8.0, performance PK. For more information, please follow other related articles on the PHP Chinese website!

Stored procedures are precompiled SQL statements in MySQL for improving performance and simplifying complex operations. 1. Improve performance: After the first compilation, subsequent calls do not need to be recompiled. 2. Improve security: Restrict data table access through permission control. 3. Simplify complex operations: combine multiple SQL statements to simplify application layer logic.

The working principle of MySQL query cache is to store the results of SELECT query, and when the same query is executed again, the cached results are directly returned. 1) Query cache improves database reading performance and finds cached results through hash values. 2) Simple configuration, set query_cache_type and query_cache_size in MySQL configuration file. 3) Use the SQL_NO_CACHE keyword to disable the cache of specific queries. 4) In high-frequency update environments, query cache may cause performance bottlenecks and needs to be optimized for use through monitoring and adjustment of parameters.

The reasons why MySQL is widely used in various projects include: 1. High performance and scalability, supporting multiple storage engines; 2. Easy to use and maintain, simple configuration and rich tools; 3. Rich ecosystem, attracting a large number of community and third-party tool support; 4. Cross-platform support, suitable for multiple operating systems.

The steps for upgrading MySQL database include: 1. Backup the database, 2. Stop the current MySQL service, 3. Install the new version of MySQL, 4. Start the new version of MySQL service, 5. Recover the database. Compatibility issues are required during the upgrade process, and advanced tools such as PerconaToolkit can be used for testing and optimization.

MySQL backup policies include logical backup, physical backup, incremental backup, replication-based backup, and cloud backup. 1. Logical backup uses mysqldump to export database structure and data, which is suitable for small databases and version migrations. 2. Physical backups are fast and comprehensive by copying data files, but require database consistency. 3. Incremental backup uses binary logging to record changes, which is suitable for large databases. 4. Replication-based backup reduces the impact on the production system by backing up from the server. 5. Cloud backups such as AmazonRDS provide automation solutions, but costs and control need to be considered. When selecting a policy, database size, downtime tolerance, recovery time, and recovery point goals should be considered.

MySQLclusteringenhancesdatabaserobustnessandscalabilitybydistributingdataacrossmultiplenodes.ItusestheNDBenginefordatareplicationandfaulttolerance,ensuringhighavailability.Setupinvolvesconfiguringmanagement,data,andSQLnodes,withcarefulmonitoringandpe

Optimizing database schema design in MySQL can improve performance through the following steps: 1. Index optimization: Create indexes on common query columns, balancing the overhead of query and inserting updates. 2. Table structure optimization: Reduce data redundancy through normalization or anti-normalization and improve access efficiency. 3. Data type selection: Use appropriate data types, such as INT instead of VARCHAR, to reduce storage space. 4. Partitioning and sub-table: For large data volumes, use partitioning and sub-table to disperse data to improve query and maintenance efficiency.

TooptimizeMySQLperformance,followthesesteps:1)Implementproperindexingtospeedupqueries,2)UseEXPLAINtoanalyzeandoptimizequeryperformance,3)Adjustserverconfigurationsettingslikeinnodb_buffer_pool_sizeandmax_connections,4)Usepartitioningforlargetablestoi


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

SAP NetWeaver Server Adapter for Eclipse
Integrate Eclipse with SAP NetWeaver application server.

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

SublimeText3 Chinese version
Chinese version, very easy to use

Dreamweaver CS6
Visual web development tools

Atom editor mac version download
The most popular open source editor
