我有 22GB
的大型数据库。我曾经使用 mysqldump
命令以 gzip 格式进行备份。
当我提取 gz 文件时,它会生成 .sql
文件 16.2GB
当我尝试在本地服务器中导入数据库时,导入大约需要 48 小时。有没有办法提高导入过程的速度?
另外我想知道是否需要进行任何硬件更改以提高性能。
当前系统配置
Processor: 4th Gen i5
RAM: 8GB
#更新
my.cnf如下
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html
# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock
# Here is entries for some specific programs
# The following values assume you have at least 32M ram
# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0
[mysqld]
#
# * Basic Settings
#
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = 127.0.0.1
#
# * Fine Tuning
#
key_buffer = 16M
max_allowed_packet = 512M
thread_stack = 192K
thread_cache_size = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover = BACKUP
#max_connections = 100
#table_cache = 64
#thread_concurrency = 10
#
# * Query Cache Configuration
#
query_cache_limit = 4M
query_cache_size = 512M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file = /var/log/mysql/mysql.log
#general_log = 1
#
# Error log - should be very few entries.
#
log_error = /var/log/mysql/error.log
#
# Here you can see queries with especially long duration
#log_slow_queries = /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
# other settings you may need to change.
#server-id = 1
#log_bin = /var/log/mysql/mysql-bin.log
expire_logs_days = 10
max_binlog_size = 100M
#binlog_do_db = include_database_name
#binlog_ignore_db = include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem
[mysqldump]
quick
quote-names
max_allowed_packet = 512M
[mysql]
#no-auto-rehash # faster start of mysql but no tab completition
[isamchk]
key_buffer = 512M
#
# * IMPORTANT: Additional settings that can override those from this file!
# The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/
它正在上传 3 天,现在已导入 9.9 GB。数据库有 MyISAM
和 InnoDB
表。我可以做些什么来提高导入性能?
我尝试使用 mysqldump
以 gz 格式分别导出每个表,并通过执行以下代码的 PHP 脚本导入每个表
$dir="./";
$files = scandir($dir, 1);
array_pop($files);
array_pop($files);
$tablecount=0;
foreach($files as $file){
$tablecount++;
echo $tablecount." ";
echo $file."\n";
$command="gunzip < ".$file." | mysql -u root -pubuntu cms";
echo exec($command);
}
原文由 dharanbro 发布,翻译遵循 CC BY-SA 4.0 许可协议
有很多参数缺失,要全面了解问题的原因。如:
还有很多。
因此,我会尝试猜测您的问题出在磁盘上,因为我管理着 150 个 MySQL 实例,其中一个实例上有 3TB 数据,通常磁盘是问题所在
现在到解决方案:
首先 - 你的 MySQL 没有配置为最佳性能。
您可以在 Percona 博客文章中了解要配置的最重要设置: http ://www.percona.com/blog/2014/01/28/10-mysql-settings-to-tune-after-installation/
特别检查参数:
如果您的问题是磁盘 - 从同一驱动器读取文件 - 会使问题变得更糟。
如果您的 MySQL 服务器因为没有足够的可用 RAM 而开始交换 - 您的问题会变得更大。
您需要在恢复过程之前和期间在您的机器上运行诊断程序以找出答案。
此外,我可以建议您使用另一种技术来执行重建任务,它比 mysqldump 运行得更快。
它是 Percona Xtrabackup - http://www.percona.com/doc/percona-xtrabackup/2.2/
您将需要使用它创建备份,并从中恢复,或者使用流选项直接从正在运行的服务器重建。
此外,从 5.5 开始的 MySQL 版本 - InnoDB 的执行速度比 MyISAM 快。考虑将所有表格更改为它。