Hallo,
ich habe eben das Tuning-Primer Script mal ausgeführt, da ich mir dachte, einfach noch was aus der Kiste rauszuholen, dann steht meistens unten "Your table lockung seems to be fine", nur damit weiß ich doch nicht genau, wo bzw. was ich verändern muss?
Bitte nicht so hart rangehen, ich weiß hört für euch Profis alles so einfach an, dachte aber einfach mal zu fragen denn - Fragen kostet nix
Hier der Auszug:
ich habe eben das Tuning-Primer Script mal ausgeführt, da ich mir dachte, einfach noch was aus der Kiste rauszuholen, dann steht meistens unten "Your table lockung seems to be fine", nur damit weiß ich doch nicht genau, wo bzw. was ich verändern muss?
Bitte nicht so hart rangehen, ich weiß hört für euch Profis alles so einfach an, dachte aber einfach mal zu fragen denn - Fragen kostet nix
Hier der Auszug:
Code:
vs162054:/usr/bin # wget http://www.day32.com/MySQL/tuning-primer.sh
--19:07:48-- http://www.day32.com/MySQL/tuning-primer.sh
=> `tuning-primer.sh'
Resolving www.day32.com... 74.52.59.194
Connecting to www.day32.com|74.52.59.194|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 42,596 (42K) [application/x-sh]
100%[====================================>] 42,596 66.13K/s
19:07:51 (65.83 KB/s) - `tuning-primer.sh' saved [42596/42596]
vs162054:/usr/bin # chmod 755 tuning-primer.sh
vs162054:/usr/bin # tuning-primer.sh
-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -
MySQL Version 4.1.10a i686
/usr/bin/tuning-primer.sh: line 382: bc: command not found
/usr/bin/tuning-primer.sh: line 383: bc: command not found
/usr/bin/tuning-primer.sh: line 384: bc: command not found
/usr/bin/tuning-primer.sh: line 385: bc: command not found
/usr/bin/tuning-primer.sh: line 386: bc: command not found
/usr/bin/tuning-primer.sh: line 387: bc: command not found
Uptime = days hrs min sec
Avg. qps = 3
Total Questions = 329364
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 329376 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 = 4
The number of used connections is 4% 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 1117: bc: command not found
/usr/bin/tuning-primer.sh: line 1118: bc: command not found
/usr/bin/tuning-primer.sh: line 1142: bc: command not found
/usr/bin/tuning-primer.sh: line 1145: bc: command not found
/usr/bin/tuning-primer.sh: line 1146: bc: command not found
/usr/bin/tuning-primer.sh: line 1148: 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 325: 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 325: bc: command not found
/usr/bin/tuning-primer.sh: line 599: bc: command not found
/usr/bin/tuning-primer.sh: line 600: bc: command not found
/usr/bin/tuning-primer.sh: line 325: bc: command not found
Current MyISAM index space = M
/usr/bin/tuning-primer.sh: line 325: bc: command not found
Current key_buffer_size = M
Key cache miss rate is 1 : 111
Key buffer fill ratio = %
/usr/bin/tuning-primer.sh: line 619: [: -ge: unary operator expected
/usr/bin/tuning-primer.sh: line 623: [: -le: unary operator expected
Your key_buffer_size seems to be fine
QUERY CACHE
Query cache is supported but not enabled
Perhaps you should set the query_cache_size
SORT OPERATIONS
/usr/bin/tuning-primer.sh: line 325: bc: command not found
Current sort_buffer_size = K
/usr/bin/tuning-primer.sh: line 325: bc: command not found
Current record/read_rnd_buffer_size = K
Sort buffer seems to be fine
JOINS
/usr/bin/tuning-primer.sh: line 325: bc: command not found
Current join_buffer_size = K
You have had 193 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 = 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 354 tables
You have 64 open tables.
Current table_cache hit rate is 1%, while 100% of your table cache is in use
You should probably increase your table_cache
TEMP TABLES
/usr/bin/tuning-primer.sh: line 325: bc: command not found
Current max_heap_table_size = M
/usr/bin/tuning-primer.sh: line 325: bc: command not found
Current tmp_table_size = M
Of 10189 temp tables, 63% were created on disk
Effective in-memory tmp_table_size is limited to max_heap_table_size.
Perhaps you should increase your tmp_table_size and/or max_heap_table_size
to reduce the number of disk-based temporary tables
Note! BLOB and TEXT columns are not allow in memory tables.
If you are using these columns raising these values might not impact your
ratio of on disk temp tables.
TABLE SCANS
/usr/bin/tuning-primer.sh: line 325: bc: command not found
Current read_buffer_size = K
Current table scan ratio = 21 : 1
read_buffer_size seems to be fine
TABLE LOCKING
Current Lock Wait ratio = 0 : 329476
Your table locking seems to be fine
