# mysqltuner >> MySQLTuner 1.6.0 - Major Hayden >> Bug reports, feature requests, and downloads at http://mysqltuner.com/ >> Run with '--help' for additional options and output filtering [--] Skipped version check for MySQLTuner script mysql: [Warning] Using a password on the command line interface can be insecure. [OK] Currently running supported MySQL version 5.7.17 [OK] Operating on 64-bit architecture -------- Storage Engine Statistics ------------------------------------------- mysql: [Warning] Using a password on the command line interface can be insecure. [--] Status: +ARCHIVE +BLACKHOLE +CSV -FEDERATED +InnoDB +MRG_MYISAM mysql: [Warning] Using a password on the command line interface can be insecure. [--] Data in MyISAM tables: 15M (Tables: 23) [--] Data in InnoDB tables: 1G (Tables: 1087) [--] Data in MEMORY tables: 1M (Tables: 31) [!!] Total fragmented tables: 39 mysql: [Warning] Using a password on the command line interface can be insecure. -------- Security Recommendations ------------------------------------------- mysql: [Warning] Using a password on the command line interface can be insecure. [OK] There is no anonymous account in all database users mysql: [Warning] Using a password on the command line interface can be insecure. ERROR 1054 (42S22) at line 1: Unknown column 'password' in 'where clause' [OK] All database users have passwords assigned mysql: [Warning] Using a password on the command line interface can be insecure. ERROR 1054 (42S22) at line 1: Unknown column 'password' in 'where clause' mysql: [Warning] Using a password on the command line interface can be insecure. [!!] User 'fw_wb23v_user@%' hasn't specific host restriction. [!!] User 'wg_wb23v_user@%' hasn't specific host restriction. [!!] There is not basic password file list ! mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. -------- Performance Metrics ------------------------------------------------- [--] Up for: 13h 1m 39s (1M q [32.327 qps], 10K conn, TX: 602M, RX: 1B) [--] Reads / Writes: 66% / 34% [--] Binary logging is disabled [--] Total buffers: 169.0M global + 1.1M per thread (151 max threads) [OK] Maximum reached memory usage: 182.5M (0.28% of installed RAM) [OK] Maximum possible memory usage: 338.9M (0.53% of installed RAM) [OK] Slow queries: 0% (0/1M) [OK] Highest usage of available connections: 7% (12/151) [OK] Aborted connections: 0.06% (6/10703) [!!] Query cache is disabled [OK] Sorts requiring temporary tables: 0% (8 temp sorts / 5K sorts) [!!] Joins performed without indexes: 9796 [!!] Temporary tables created on disk: 79% (21K on disk / 27K total) [OK] Thread cache hit rate: 99% (13 created / 10K connections) [!!] Table cache hit rate: 11% (2K open / 17K opened) [OK] Open file limit used: 0% (32/5K) [OK] Table locks acquired immediately: 100% (608 immediate / 608 locks) -------- MyISAM Metrics ----------------------------------------------------- [!!] Key buffer used: 18.5% (1M used / 8M cache) [OK] Key buffer size / total MyISAM indexes: 8.0M/2.6M [OK] Read Key buffer hit rate: 99.9% (723K cached / 1K reads) [OK] Write Key buffer hit rate: 95.2% (293K cached / 14K writes) -------- InnoDB Metrics ----------------------------------------------------- [--] InnoDB is enabled. [!!] InnoDB buffer pool / data size: 128.0M/1.3G [OK] InnoDB buffer pool instances: 1 [OK] InnoDB Used buffer: 87.49% (7167 used/ 8192 total) [OK] InnoDB Read buffer efficiency: 99.99% (310005411 hits/ 310038289 total) [!!] InnoDB Write buffer efficiency: 0.00% (0 hits/ 1 total) [OK] InnoDB log waits: 0.00% (0 waits / 13634 writes) -------- AriaDB Metrics ----------------------------------------------------- [--] AriaDB is disabled. -------- Replication Metrics ------------------------------------------------- [--] No replication slave(s) for this server. [--] This is a standalone server.. -------- Recommendations ----------------------------------------------------- General recommendations: Run OPTIMIZE TABLE to defragment tables for better performance Restrict Host for user@% to user@SpecificDNSorIp MySQL started within last 24 hours - recommendations may be inaccurate Adjust your join queries to always utilize indexes When making adjustments, make tmp_table_size/max_heap_table_size equal Reduce your SELECT DISTINCT queries which have no LIMIT clause Increase table_open_cache gradually to avoid file descriptor limits Read this before increasing table_open_cache over 64: http://bit.ly/1mi7c4C Beware that open_files_limit (5000) variable should be greater than table_open_cache ( 2000) Variables to adjust: query_cache_type (=1) join_buffer_size (> 256.0K, or always use indexes with joins) tmp_table_size (> 16M) max_heap_table_size (> 16M) table_open_cache (> 2000) innodb_buffer_pool_size (>= 1G) if possible.