I need help optimizing MySQL
Mysql cpu load to high 190%, Query very slow, 20% load RAM, browsing very slow
Server:
Intel(R) Xeon(R) CPU E5-2680 v4 @ 2.40GHz x 16
32 GB RAM
./tuning-primer.sh
And [COD]
-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -
MySQL Version 10.3.34-MariaDB-cll-lve x86_64
Uptime = 0 days 1 hrs 16 min 25 sec
Avg. qps = 383
Total Questions = 1756315
Threads Connected = 6
Warning: Server has not been running for at least 48hrs.
It may not be safe to use these recommendations
To find out more information on how each of these
runtime variables effects performance visit:
http://dev.mysql.com/doc/refman/10.3/en/server-system-variables.html
Visit http://www.mysql.com/products/enterprise/advisors.html
for info about MySQL's Enterprise Monitoring and Advisory Service
SLOW QUERIES
The slow query log is NOT enabled.
BINARY UPDATE LOG
The binary update log is NOT enabled.
You will not be able to do point in time recovery
See http://dev.mysql.com/doc/refman/10.3/en/point-in-time-recovery.html
WORKER THREADS
Current thread_cache_size = 1024
Current threads_cached = 32
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine
MAX CONNECTIONS
Current max_connections = 2500
Current threads_connected = 6
Historic max_used_connections = 38
The number of used connections is 1% of the configured maximum.
You are using less than 10% of your configured max_connections.
Lowering max_connections could help to avoid an over-allocation of memory
See "MEMORY USAGE" section to make sure you are not over-allocating
INNODB STATUS
Current InnoDB index space = 3.33 G
Current InnoDB data space = 4.54 G
Current InnoDB buffer pool free = 59 %
Current innodb_buffer_pool_size = 12.00 G
Depending on how much space your innodb indexes take up it may be safe
to increase this value to up to 2 / 3 of total system memory
MEMORY USAGE
Max Memory Ever Allocated : 12.71 G
Configured Max Per-thread Buffers : 4.35 G
Configured Max Global Buffers : 12.64 G
Configured Max Memory Limit : 17.00 G
Physical Memory : 31.25 G
Max memory limit seem to be within acceptable norms
KEY BUFFER
Current MyISAM index space = 963 M
Current key_buffer_size = 512 M
Key cache miss rate is 1 : 89
Key buffer free ratio = 78 %
Your key_buffer_size seems to be fine
QUERY CACHE
Query cache is enabled
Current query_cache_size = 128 M
Current query_cache_used = 59 M
Current query_cache_limit = 4 M
Current Query cache Memory fill ratio = 46.38 %
Current query_cache_min_res_unit = 4 K
MySQL won't cache query results that are larger than query_cache_limit in size
SORT OPERATIONS
Current sort_buffer_size = 128 K
Current read_rnd_buffer_size = 256 K
Sort buffer seems to be fine
JOINS
Current join_buffer_size = 1.00 M
You have had 22 queries where a join could not use an index properly
You should enable "log-queries-not-using-indexes"
Then look for non indexed joins in the slow query log.
If you are unable to optimize your queries you may want to increase your
join_buffer_size to accommodate larger joins in one pass.
Note! This script will still suggest raising the join_buffer_size when
ANY joins not using indexes are found.
OPEN FILES LIMIT
Current open_files_limit = 40000 files
The open_files_limit should typically be set to at least 2x-3x
that of table_cache if you have heavy MyISAM usage.
Your open_files_limit value seems to be fine
TABLE CACHE
Current table_open_cache = 3072 tables
Current table_definition_cache = 2048 tables
You have a total of 2371 tables
You have 2534 open tables.
The table_cache value seems to be fine
You should probably increase your table_definition_cache value.
TEMP TABLES
Current max_heap_table_size = 128 M
Current tmp_table_size = 128 M
Of 102688 temp tables, 14% were created on disk
Created disk tmp tables ratio seems fine
TABLE SCANS
Current read_buffer_size = 128 K
Current table scan ratio = 381 : 1
read_buffer_size seems to be fine
TABLE LOCKING
Current Lock Wait ratio = 1 : 489
You may benefit from selective use of InnoDB.
If you have long-running SELECT's against MyISAM tables and perform
frequent updates consider setting 'low_priority_updates=1'
If you have a high concurrency of inserts on Dynamic row-length tables
consider setting 'concurrent_insert=ALWAYS'.
And [COD]
-
Hey there! The MySQL server hadn't even been running for 2 hours according to the output from the tuning script, so the information may not be accurate, as it says. When the server seems slow, what is the output from the following command: mysqladmin proc status0 -
Hey there! The MySQL server hadn't even been running for 2 hours according to the output from the tuning script, so the information may not be accurate, as it says. When the server seems slow, what is the output from the following command:
mysqladmin proc status
I rebooted because of the slowness. Output results below:+-----+--------------------------+-----------+--------------------------+---------+------+--------------------------+------------------------------------------------------------------------------------------------------+----------+ | Id | User | Host | db | Command | Time | State | Info | Progress | +-----+--------------------------+-----------+--------------------------+---------+------+--------------------------+------------------------------------------------------------------------------------------------------+----------+ | 1 | system user | | | Daemon | | InnoDB purge coordinator | | 0.000 | | 2 | system user | | | Daemon | | InnoDB purge worker | | 0.000 | | 3 | system user | | | Daemon | | InnoDB purge worker | | 0.000 | | 4 | system user | | | Daemon | | InnoDB purge worker | | 0.000 | | 5 | system user | | | Daemon | | InnoDB shutdown handler | | 0.000 | | 9 | root | localhost | information_schema | Sleep | 14 | | | 0.000 | | 11 | root | localhost | information_schema | Sleep | 314 | | | 0.000 | | 13 | root | localhost | information_schema | Sleep | 14 | | | 0.000 | | 440 | kohlassyedek_kohlassyeni | localhost | kohlassyedek_kohlassyeni | Query | 0 | Sending data | SELECT COUNT(*) FROM UVspU9aX_term_relationships, UVspU9aX_posts WHERE UVspU9aX_posts.ID = UVspU9aX_ | 0.000 | | 445 | kohlassyedek_kohlassyeni | localhost | kohlassyedek_kohlassyeni | Query | 0 | Sending data | SELECT post_status, COUNT( * ) AS num_posts FROM UVspU9aX_posts WHERE post_type = 'product' GROUP BY | 0.000 | | 446 | root | localhost | | Query | 0 | Init | show processlist | 0.000 | +-----+--------------------------+-----------+--------------------------+---------+------+--------------------------+------------------------------------------------------------------------------------------------------+----------+ Uptime: 324 Threads: 39 Questions: 96924 Slow queries: 19 Opens: 308 Flush tables: 1 Open tables: 301 Queries per second avg: 299.1480 -
It usually isn't necessary to reboot a system because of slowness, as restarting a particular service will often take care of that. Nothing in the output you provided looks odd, but was the slowness happening again when you ran that command? We need to run the commands and examine the system while the slowness is happening, as it will be very difficult to get useful data after it has stopped. 0 -
It usually isn't necessary to reboot a system because of slowness, as restarting a particular service will often take care of that. Nothing in the output you provided looks odd, but was the slowness happening again when you ran that command? We need to run the commands and examine the system while the slowness is happening, as it will be very difficult to get useful data after it has stopped.
First of all, thanks I made a few changes, I'm watching the processes, it seems there is no problem.0 -
It's always possible it could have been a temporary issue with the MySQL service, but if you see it happening again just try and run those tools and see if they give you more information. 0
Please sign in to leave a comment.
Comments
5 comments