mysql consumindo muita cpu

[meleca123 0]

bom pessoal estou usando esta configuração no meu servidor porem esta usando muito a cpu

 

olha que o pc não é dos mais ruim

configuração do servidor

Xeon E3 1230v3 e 32 gigas de memoria usando disco SD mesmo assim consumindo muita memoria

fica aqui meu my.cnf para alquiem poder verificar o que estou fazendo de errado obrigado

#
# 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              = 200g
max_allowed_packet      = 999M
thread_stack            = 128K
thread_cache_size       = 81111
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover         = BACKUP
max_connections         = 10000
table_cache            = 10000
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
query_cache_limit	= 999M
query_cache_size        = 999M
#
# * 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 logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.
#
# 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	= 16M

[mysql]
#no-auto-rehash	# faster start of mysql but no tab completition

[isamchk]
key_buffer		= 200g
[mysqld]
long_query_time         = 10
log-slow-queries        = /var/log/mysql/mysql-slow.log

#
# * 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/

[-=Érico=- 5]

Depende muito do que você vai estar rodando nesse servidor.

 

10.000 conexões simultâneas até para servidores que rodam sistemas com bastante concorrência é considerado muito. Com os outros valores que você têm configurado se você tem 10.000 conexões simultâneas fazendo consultas em um banco de dados de tamanho médio simplesmente 32GB de RAM não vai dar conta nem de perto.

 

Referente a CPU, o que pode estar causando o consumo são os valores thread_stack e thread_cache_size e thread_concurrency.

Dê uma olhada nesses valores no manual, os valores que você está usando com certeza devem ser alterados.

Se você não usa Solaris ou está usando MySQL >= 5.6.1, não se preocupe com thread_concurrency, ele não faz nada.

Mas tem outras variáveis que podem afetar bastante o consumo de CPU, principalmente se você está usando InnoDB, como innodb_thread_concurrency, innodb_io_capacity, innodb_write_io_threads e innodb_read_io_threads.

Dá uma olhada no manual do MySQL e procura essa variáveis.