Skip to main content

Optimize MySQL Help

Comments

2 comments

  • cPanelMichael
    Hello :) Ensure you let MySQL run for at least 24 hours before running a tuner to obtain accurate results. Thank you.
    0
  • Filipe Barreto

    >> MySQLTuner 1.1.1 - Major Hayden >> 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 [!!] Your MySQL version 10.0.14-MariaDB-1~trusty-wsrep is EOL software! Upgrade soon! [OK] Operating on 64-bit architecture -------- Storage Engine Statistics ------------------------------------------- [--] Status: +Archive -BDB +Federated +InnoDB -ISAM -NDBCluster [--] Data in CSV tables: 0B (Tables: 2) [--] Data in PERFORMANCE_SCHEMA tables: 0B (Tables: 52) [--] Data in InnoDB tables: 1G (Tables: 196) [--] Data in MyISAM tables: 1G (Tables: 125) [!!] Total fragmented tables: 36 -------- Security Recommendations ------------------------------------------- [OK] All database users have passwords assigned Use of uninitialized value in addition (+) at /usr/bin/mysqltuner line 567 (#1) (W uninitialized) An undefined value was used as if it were already defined. It was interpreted as a "" or a 0, but maybe it was a mistake. To suppress this warning assign a defined value to your variables. To help you figure out what was undefined, perl will try to tell you the name of the variable (if any) that was undefined. In some cases it cannot do this, so it also tells you what operation you used the undefined value in. Note, however, that perl optimizes your program anid the operation displayed in the warning may not necessarily appear literally in your program. For example, "that $foo" is usually optimized into "that " . $foo, and the warning will refer to the concatenation (.) operator, even though there is no . in your program. -------- Performance Metrics ------------------------------------------------- [--] Up for: 7d 12h 8m 0s (18M q [28.455 qps], 985K conn, TX: 58B, RX: 13B) [--] Reads / Writes: 88% / 12% [--] Total buffers: 4.3G global + 416.0K per thread (350 max threads) [OK] Maximum possible memory usage: 4.4G (32% of installed RAM) [OK] Slow queries: 5% (1M/18M) [!!] Highest connection usage: 91% (319/350) [OK] Key buffer size / total MyISAM indexes: 2.0G/2.8G [OK] Key buffer hit rate: 100.0% (45B cached / 4M reads) [OK] Sorts requiring temporary tables: 0% (8K temp sorts / 2M sorts) [!!] Joins performed without indexes: 1437892 [OK] Temporary tables created on disk: 8% (400K on disk / 4M total) [OK] Thread cache hit rate: 91% (83K created / 985K connections) [!!] Table cache hit rate: 4% (893 open / 19K opened) Use of uninitialized value $myvar{"table_cache"} in concatenation (.) or string at /usr/bin/mysqltuner line 851 (#1) [OK] Open file limit used: 0% (460/65K) [OK] Table locks acquired immediately: 98% (58M immediate / 59M locks) [!!] Connections aborted: 31% [OK] InnoDB data size / buffer pool: 1.4G/2.0G -------- Recommendations ----------------------------------------------------- General recommendations: Run OPTIMIZE TABLE to defragment tables for better performance Reduce or eliminate persistent connections to reduce connection usage Upgrade MySQL to version 4+ to utilize query caching Adjust your join queries to always utilize indexes Increase table_cache gradually to avoid file descriptor limits Your applications are not closing MySQL connections properly Variables to adjust: max_connections (> 350) wait_timeout (< 180) interactive_timeout (< 180) join_buffer_size (> 128.0K, or always use indexes with joins) table_cache (> )
    0

Please sign in to leave a comment.