Zitat:
Zitat von Spin-Doc |
mysqltuner.pl und mysql-primer.sh sind bereits installiert.
Auszug aus mysqltuner.pl:
Code:
>> MySQLTuner 1.0.1 - Major Hayden <major@mhtx.net>
>> Bug reports, feature requests, and downloads at http://mysqltuner.com/
>> Run with '--help' for additional options and output filtering
-------- General Statistics --------------------------------------------------
[--] Skipped version check for MySQLTuner script
[OK] Currently running supported MySQL version 5.1.66-0+squeeze1
[OK] Operating on 64-bit architecture
-------- Storage Engine Statistics -------------------------------------------
[--] Status: -Archive -BDB -Federated +InnoDB -ISAM -NDBCluster
[--] Data in MyISAM tables: 48M (Tables: 110)
[--] Data in InnoDB tables: 4G (Tables: 216)
[--] Data in MEMORY tables: 4M (Tables: 6)
[!!] Total fragmented tables: 218
-------- Performance Metrics -------------------------------------------------
[--] Up for: 6h 46m 22s (31M q [1K qps], 155K conn, TX: 5B, RX: 2B)
[--] Reads / Writes: 98% / 2%
[--] Total buffers: 47.8G global + 10.2M per thread (3000 max threads)
[!!] Maximum possible memory usage: 77.6G (124% of installed RAM)
[OK] Slow queries: 0% (80K/31M)
[OK] Highest usage of available connections: 27% (827/3000)
[OK] Key buffer size / total MyISAM indexes: 256.0M/56.5M
[OK] Key buffer hit rate: 95.5% (6M cached / 314K reads)
[!!] Query cache efficiency: 10.7% (3M cached / 28M selects)
[OK] Query cache prunes per day: 0
[OK] Sorts requiring temporary tables: 2% (6K temp sorts / 295K sorts)
[!!] Temporary tables created on disk: 49% (212K on disk / 425K total)
[OK] Thread cache hit rate: 98% (1K created / 155K connections)
[OK] Table cache hit rate: 47% (1K open / 2K opened)
[OK] Open file limit used: 0% (267/68K)
[OK] Table locks acquired immediately: 99% (27M immediate / 27M locks)
[OK] InnoDB data size / buffer pool: 4.6G/43.0G
-------- Recommendations -----------------------------------------------------
General recommendations:
Run OPTIMIZE TABLE to defragment tables for better performance
MySQL started within last 24 hours - recommendations may be inaccurate
Reduce your overall MySQL memory footprint for system stability
Enable the slow query log to troubleshoot bad queries
Temporary table size is already large - reduce result set size
Reduce your SELECT DISTINCT queries without LIMIT clauses
Variables to adjust:
*** MySQL's maximum memory usage is dangerously high ***
*** Add RAM before increasing MySQL buffer variables ***
query_cache_limit (> 512M, or use smaller result sets) Auszug aus mysql-primer.sh:
Code:
-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -
MySQL Version 5.1.66-0+squeeze1 x86_64
Uptime = 0 days 6 hrs 46 min 44 sec
Avg. qps = 1295
Total Questions = 31611236
Threads Connected = 150
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.1/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 = 1.000000 sec.
You have 80313 out of 31611544 that take longer than 1.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.1/en/point-in-time-recovery.html
WORKER THREADS
Current thread_cache_size = 100
Current threads_cached = 68
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine
MAX CONNECTIONS
Current max_connections = 3000
Current threads_connected = 144
Historic max_used_connections = 827
The number of used connections is 27% of the configured maximum.
Your max_connections variable seems to be fine.
INNODB STATUS
Current InnoDB index space = 8.08 G
Current InnoDB data space = 4.64 G
Current InnoDB buffer pool free = 78 %
Current innodb_buffer_pool_size = 43.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 : 53.97 G
Configured Max Per-thread Buffers : 29.84 G
Configured Max Global Buffers : 45.75 G
Configured Max Memory Limit : 75.59 G
Physical Memory : 62.48 G
Max memory limit exceeds 90% of physical memory
KEY BUFFER
Current MyISAM index space = 56 M
Current key_buffer_size = 256 M
Key cache miss rate is 1 : 21
Key buffer free ratio = 80 %
Your key_buffer_size seems to be fine
QUERY CACHE
Query cache is enabled
Current query_cache_size = 2.00 G
Current query_cache_used = 5 M
Current query_cache_limit = 512 M
Current Query cache Memory fill ratio = .24 %
Current query_cache_min_res_unit = 4 K
Your query_cache_size seems to be too high.
Perhaps you can use these resources elsewhere
MySQL won't cache query results that are larger than query_cache_limit in size
SORT OPERATIONS
Current sort_buffer_size = 2 M
Current read_rnd_buffer_size = 1 M
Sort buffer seems to be fine
JOINS
Current join_buffer_size = 6.00 M
You have had 3 queries where a join could not use an index properly
join_buffer_size >= 4 M
This is not advised
You should enable "log-queries-not-using-indexes"
Then look for non indexed joins in the slow query log.
OPEN FILES LIMIT
Current open_files_limit = 68546 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 = 32768 tables
Current table_definition_cache = 16384 tables
You have a total of 355 tables
You have 1202 open tables.
The table_cache value seems to be fine
TEMP TABLES
Current max_heap_table_size = 2.00 G
Current tmp_table_size = 2.00 G
Of 213238 temp tables, 49% were created on disk
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
Current read_buffer_size = 1 M
Current table scan ratio = 24 : 1
read_buffer_size seems to be fine
TABLE LOCKING
Current Lock Wait ratio = 1 : 628114
Your table locking seems to be fine Wäre nett wenn jemand damit schon Erfahrung gesammelt hat und mir paar Ratschläge/Tipps geben kann.