Shulou(Shulou.com)05/31 Report--

This article will explain in detail how to compress and compare mysql dump backup files. The content of the article is of high quality, so the editor will share it with you for reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

Mysqldump, using single-transaction, gzip compression through pipes, 20g single database backup

Real8m15.291s

User8m39.617s

Sys0m16.675s

Backup file 1.43G

Mysqlpump,4 thread, using single-transaction, gzip compression through pipes, 20g single database backup

Real6m21.481s

User9m35.788s

Sys0m31.509s

Backup file 1.52G

Mysqlpump,4 thread, using single-transaction, using native LZ4 compression, 20g single database backup

Real2m1.440s

User4m34.146s

Sys0m12.712s

Backup file 1.54G

Mysqlpump,4 thread, using single-transaction, using native zlib compression, 20g single database backup

Real6m30.356s

User9m28.144s

Sys0m15.970s

Backup file 2.39G

1Jing LZ4 is the fastest, but the backup file is the largest. If the database is less than 50 gigabytes, consider using zlib or gzip.

2, because the current compression can only use single-thread, small database, single-thread mysqldump will not be much slower than mysqlpump.

3. Mysqlpump is the first choice for large databases with LZ4 compression, which has obvious time advantage.

4the backup file lacks SET @ @ GLOBAL.GTID_PURGED related statements, which is not suitable for building master-slave replication environment based on GTID.

On how to compare the compression of mysql dump backup files to share here, I hope that the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.