全球主机交流论坛
标题:
8G8H内存的阿里云服务器,请各位帮忙看看mysql设置合理不?
[打印本页]
作者:
amo
时间:
2018-6-7 15:24
标题:
8G8H内存的阿里云服务器,请各位帮忙看看mysql设置合理不?
本帖最后由 amo 于 2018-6-7 15:25 编辑
OS:CentOS 6.5
Nginx:1.0.15
MySQL:5.1.69
# Example MySQL config file for very large systems.
#
# This is for a large system with memory of 1G-2G where the system runs mainly
# MySQL.
#
# MySQL programs look for option files in a set of
# locations which depend on the deployment platform.
# You can copy this option file to one of those
# locations. For information about these locations, see:
# http://dev.mysql.com/doc/mysql/en/option-files.html
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.
# The following options will be passed to all MySQL clients
[client]
#password = your_password
port = 3306
socket = /tmp/mysql.sock
# Here follows entries for some specific programs
# The MySQL server
[mysqld]
#lum_config_start
wait_timeout=888888
interactive_timeout=888888
max_connections=1000
back_log=500
key_buffer_size=3840MB
sort_buffer_size=32MB
read_buffer_size=32MB
join_buffer_size=2MB
thread_cache_size=32
query_cache_size=256MB
#lum_config_end
port = 3306
socket = /tmp/mysql.sock
skip-locking
max_allowed_packet = 1M
table_open_cache = 512
read_rnd_buffer_size = 8M
myisam_sort_buffer_size = 64M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 8
# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking
# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin
# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id = 1
# Replication Slave (comment out master section to use this)
#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
# where you replace <host>, <user>, <password> by quoted strings and
# <port> by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_HOST='*.*.*.*', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-host = <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password = <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin
#
# binary logging format - mixed recommended
#binlog_format=mixed
# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /usr/local/mysql/var
#innodb_data_file_path = ibdata1:2000M;ibdata2:10M:autoextend
#innodb_log_group_home_dir = /usr/local/mysql/var
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 384M
#innodb_additional_mem_pool_size = 20M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 100M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50
[mysqldump]
quick
max_allowed_packet = 16M
[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates
[myisamchk]
read_buffer = 2M
write_buffer = 2M
[mysqlhotcopy]
interactive-timeout
复制代码
作者:
liutianshu77
时间:
2018-6-7 15:42
提示:
作者被禁止或删除 内容自动屏蔽
作者:
Sooele
时间:
2018-6-7 16:10
5.1。。都8.0了。最起码也5
作者:
the2ndface
时间:
2018-6-7 16:11
楼上说的对,当然,如果早期数据需要迁移,用的是这个版本,那还是继续用吧
作者:
可乐呀
时间:
2018-6-7 16:14
上centos7和mysql5.7吧、、、、
作者:
amo
时间:
2018-6-7 16:33
几年前的服务器了,上面东西很多,不好迁移啊 怕出问题。。
另外关于mysql优化网上说法千人千面。。
http://www.jb51.net/article/119515.htm
https://**blogs.com/52php/p/5675350.html
https://www.linuxidc.com/Linux/2017-07/145868.htm
http://www.jb51.net/article/83569.htm
好纠结
作者:
zhoutiancai
时间:
2018-6-7 17:17
花钱买云数据库
欢迎光临 全球主机交流论坛 (https://sunk.eu.org/)
Powered by Discuz! X3.4