Hi alle zusammen
Mein Apache und Mysql lahmen ein wenig
Hab mal tuning primer script lauffen lassen
Das kommt dann rauß
Könnt ihr mir bitte mal ein wenig helfen was ich alles ändern soll
Die Kiste ist ein RootDS mit 1,5 GHZ und 1GB Ram
gruß Chris
Mein Apache und Mysql lahmen ein wenig
Hab mal tuning primer script lauffen lassen
Das kommt dann rauß
HTML:
-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -
MySQL Version 4.0.24_Debian-10sarge2-log is EOL please upgrade to MySQL 4.1 or later
/usr/bin/tuning-primer.sh: line 1: bc: command not found
/usr/bin/tuning-primer.sh: line 1: bc: command not found
/usr/bin/tuning-primer.sh: line 1: bc: command not found
/usr/bin/tuning-primer.sh: line 1: bc: command not found
/usr/bin/tuning-primer.sh: line 1: bc: command not found
/usr/bin/tuning-primer.sh: line 1: bc: command not found
Uptime = days hrs min sec
Avg. qps = 48
Total Questions = 71057
Threads Connected = 1
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/4.1/en/server-system-variables.html
SLOW QUERIES
Current long_query_time = 10 sec.
You have 0 out of 71069 that take longer than 10 sec. to complete
The slow query log is NOT enabled.
Your long_query_time may be too high, I typically set this under 5 sec.
WORKER THREADS
Current thread_cache_size = 0
Current threads_cached = 0
Current threads_per_sec = 1
Historic threads_per_sec = 0
Your thread_cache_size is fine
MAX CONNECTIONS
Current max_connections = 100
Current threads_connected = 1
Historic max_used_connections = 8
The number of used connections is 8% 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
MEMORY USAGE
/usr/bin/tuning-primer.sh: line 1: bc: command not found
/usr/bin/tuning-primer.sh: line 1: bc: command not found
/usr/bin/tuning-primer.sh: line 1: bc: command not found
/usr/bin/tuning-primer.sh: line 1: bc: command not found
/usr/bin/tuning-primer.sh: line 1: bc: command not found
/usr/bin/tuning-primer.sh: line 1: bc: command not found
/usr/bin/tuning-primer.sh: line 1150: [: -gt: unary operator expected
/usr/bin/tuning-primer.sh: line 344: [: max_memoryHR: integer expression expected
/usr/bin/tuning-primer.sh: line 350: [: max_memoryHR: integer expression expected
/usr/bin/tuning-primer.sh: line 356: [: max_memoryHR: integer expression expected
/usr/bin/tuning-primer.sh: line 363: export: `0=max_memoryHR': not a valid identifier
Max Memory Ever Allocated : bytes
/usr/bin/tuning-primer.sh: line 344: [: per_thread_buffersHR: integer expression expected
/usr/bin/tuning-primer.sh: line 350: [: per_thread_buffersHR: integer expression expected
/usr/bin/tuning-primer.sh: line 356: [: per_thread_buffersHR: integer expression expected
/usr/bin/tuning-primer.sh: line 363: export: `0=per_thread_buffersHR': not a valid identifier
Configured Max Per-thread Buffers : bytes
/usr/bin/tuning-primer.sh: line 344: [: global_buffersHR: integer expression expected
/usr/bin/tuning-primer.sh: line 350: [: global_buffersHR: integer expression expected
/usr/bin/tuning-primer.sh: line 356: [: global_buffersHR: integer expression expected
/usr/bin/tuning-primer.sh: line 363: export: `0=global_buffersHR': not a valid identifier
Configured Max Global Buffers : bytes
/usr/bin/tuning-primer.sh: line 344: [: total_memoryHR: integer expression expected
/usr/bin/tuning-primer.sh: line 350: [: total_memoryHR: integer expression expected
/usr/bin/tuning-primer.sh: line 356: [: total_memoryHR: integer expression expected
/usr/bin/tuning-primer.sh: line 363: export: `0=total_memoryHR': not a valid identifier
Configured Max Memory Limit : bytes
/usr/bin/tuning-primer.sh: line 1: bc: command not found
Total System Memory : G
Max memory limit seem to be within acceptable norms
KEY BUFFER
/usr/bin/tuning-primer.sh: line 1: bc: command not found
Current MyISAM index space = M
/usr/bin/tuning-primer.sh: line 1: bc: command not found
Current key_buffer_size = M
Key cache miss rate is 1 : 1895
Key buffer fill ratio = Unknown %
Your key_buffer_size seems to be fine
QUERY CACHE
/usr/bin/tuning-primer.sh: line 1: bc: command not found
/usr/bin/tuning-primer.sh: line 1: bc: command not found
Query cache is enabled
/usr/bin/tuning-primer.sh: line 1: bc: command not found
Current query_cache_size = M
/usr/bin/tuning-primer.sh: line 1: bc: command not found
Current query_cache_used = M
/usr/bin/tuning-primer.sh: line 1: bc: command not found
Current query_cach_limit = M
Current Query cache fill ratio = %
/usr/bin/tuning-primer.sh: line 661: [: -le: unary operator expected
MySQL won't cache query results that are larger than query_cache_limit in size
SORT OPERATIONS
/usr/bin/tuning-primer.sh: line 1: bc: command not found
Current sort_buffer_size = M
/usr/bin/tuning-primer.sh: line 1: bc: command not found
Current record/read_rnd_buffer_size = K
Sort buffer seems to be fine
JOINS
/usr/bin/tuning-primer.sh: line 1: bc: command not found
Current join_buffer_size = K
You have had 128 queries where a join could not use an index properly
You should enable "log-long-format"
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 = 1024 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_cache value = 64 tables
You have a total of 470 tables
You have 64 open tables.
Current table_cache hit rate is 9%, while 100% of your table cache is in use
You should probably increase your table_cache
TEMP TABLES
/usr/bin/tuning-primer.sh: line 1: bc: command not found
Current max_heap_table_size = M
/usr/bin/tuning-primer.sh: line 1: bc: command not found
Current tmp_table_size = M
Of 596 temp tables, 21% were created on disk
Effective in-memory tmp_table_size is limited to max_heap_table_size.
Created disk tmp tables ratio seems fine
TABLE SCANS
/usr/bin/tuning-primer.sh: line 1: bc: command not found
Current read_buffer_size = K
Current table scan ratio = 887 : 1
read_buffer_size seems to be fine
TABLE LOCKING
Current Lock Wait ratio = 1 : 5966
Your table locking seems to be fine
Könnt ihr mir bitte mal ein wenig helfen was ich alles ändern soll
Die Kiste ist ein RootDS mit 1,5 GHZ und 1GB Ram
gruß Chris