Page 1 of 1

100% load???

Posted: Fri Jul 21, 2017 7:10 pm
by Nou4r
My Server is always on 100% CPU load, i tried playing around with the configuration but nothing helped.
My Website is very slow thanks to this and i don't even have many users right now. (300 max. Google Analytics)

Image

MySQLTuner

Code: Select all

https://pastebin.com/YS9HwrWF
tuning prime

Code: Select all


        -- MYSQL PERFORMANCE TUNING PRIMER --
             - By: Matthew Montgomery -

MySQL Version 5.5.54-0+deb8u1 x86_64

Uptime = 0 days 0 hrs 15 min 33 sec
Avg. qps = 43
Total Questions = 40522
Threads Connected = 133

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/5.5/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.
Current long_query_time = 50.000000 sec.
You have 75 out of 40632 that take longer than 50.000000 sec. to complete
Your long_query_time seems to be fine

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/5.5/en/point-in-time-recovery.html

WORKER THREADS
Current thread_cache_size = 80
Current threads_cached = 24
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine

MAX CONNECTIONS
Current max_connections = 400
Current threads_connected = 133
Historic max_used_connections = 160
The number of used connections is 40% of the configured maximum.
Your max_connections variable seems to be fine.

INNODB STATUS
Current InnoDB index space = 5 M
Current InnoDB data space = 141 M
Current InnoDB buffer pool free = 79 %
Current innodb_buffer_pool_size = 128 M
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 : 9.83 G
Configured Max Per-thread Buffers : 23.58 G
Configured Max Global Buffers : 416 M
Configured Max Memory Limit : 23.99 G
Physical Memory : 15.40 G

Max memory limit exceeds 90% of physical memory

KEY BUFFER
Current MyISAM index space = 16 M
Current key_buffer_size = 256 M
Key cache miss rate is 1 : 281
Key buffer free ratio = 81 %
Your key_buffer_size seems to be fine

QUERY CACHE
Query cache is enabled
Current query_cache_size = 16 M
Current query_cache_used = 12 M
Current query_cache_limit = 1 M
Current Query cache Memory fill ratio = 77.56 %
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 = 10 M
Current read_rnd_buffer_size = 40 M
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 132.00 K
You have had 520 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 = 2000 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 = 256 tables
Current table_definition_cache = 400 tables
You have a total of 583 tables
You have 351 open tables.
Current table_cache hit rate is 6%
, while 137% of your table cache is in use
You should probably increase your table_cache
You should probably increase your table_definition_cache value.

TEMP TABLES
Current max_heap_table_size = 16 M
Current tmp_table_size = 16 M
Of 1700 temp tables, 5% were created on disk
Created disk tmp tables ratio seems fine

TABLE SCANS
Current read_buffer_size = 10 M
Current table scan ratio = 3291909 : 1
read_buffer_size is over 8 MB there is probably no need for such a large read_buffer

TABLE LOCKING
Current Lock Wait ratio = 0 : 41480
Your table locking seems to be fine


Re: 100% load???

Posted: Sat Jul 22, 2017 2:21 pm
by Nou4r
Image
How is this even possible

Re: 100% load???

Posted: Sat Jul 22, 2017 6:07 pm
by mehargags
what kind of sites do you host ? Wordpress ?

You may be a victim of a compromised server. There are endless threads on it here. Use search and try to find out the problem.

Re: 100% load???

Posted: Mon Jul 24, 2017 12:46 pm
by skurudo
You can try to tune your mysql a little too
viewtopic.php?f=14&t=14148