8. 動作環境：
動作環境(氏の公開情報より)
MySQL 3.23, 4.0, 4.1, 5.0, 5.1 (full support) ←動作確認済み
MySQL 5.4 (not fully tested, partially supported)
MySQL 5.5 (partial support) ←動作確認済み
MySQL 5.6 (partial support) ←動作確認済み
MySQL 6.0 (partial support)
MariaDB 10.x (partial support)
Perl 5.6 or later (with perl-doc package)
9. 氏の言葉(原文)
It is extremely important for you to fully understand each change
you make to a MySQL database server. If you don't understand
portions of the script's output, or if you don't understand the
recommendations,you should consult a knowledgeable DBA or
system administrator that you trust.Always test your changes on
staging environments, and always keep in mind that improvements
in one area can negatively affect MySQL in other areas.
15. >> MySQLTuner 1.4.0 - Major Hayden <major@mhtx.net>
>> Bug reports, feature requests, and downloads at http://mysqltuner.com/
>> Run with '--help' for additional options and output filtering
Please enter your MySQL administrative login: root
Please enter your MySQL administrative password:
[OK] Currently running supported MySQL version 5.6.25
[OK] Operating on 64-bit architecture
-------- Storage Engine Statistics -------------------------------------------
[--] Status: Warning: Using a password on the command line interface can be insecure.
+ARCHIVE +BLACKHOLE +CSV -FEDERATED +InnoDB +MRG_MYISAM
Warning: Using a password on the command line interface can be insecure.
Warning: Using a password on the command line interface can be insecure.
[--] Data in MyISAM tables: 62K (Tables: 32)
[--] Data in InnoDB tables: 60M (Tables: 280)
[--] Data in PERFORMANCE_SCHEMA tables: 0B (Tables: 52)
[!!] Total fragmented tables: 10
16. -------- Security Recommendations -------------------------------------------
Warning: Using a password on the command line interface can be insecure.
[OK] All database users have passwords assigned
Warning: Using a password on the command line interface can be insecure.
-------- Performance Metrics -------------------------------------------------
[--] Up for: 2d 11h 35m 4s (252K q [1.175 qps], 5K conn, TX: 387M, RX: 97M)
[--] Reads / Writes: 59% / 41%
[--] Total buffers: 164.0M global + 1.1M per thread (151 max threads)
[OK] Maximum possible memory usage: 325.6M (17% of installed RAM)
[OK] Slow queries: 0% (0/252 connections: 1% (3/151)
[OK] Key buffer size / total MyISAM indexes: 8.0M/244.0K
[OK] Key buffer hit rate: 99.9% (793 cached / 1 reads)
[OK] Query cache efficiency: 72.5% (145K cached / 200K selects)
[!!] Query cache pru ,,,,,
22. 150610 21:59:06 mysqld_safe Number of processes running now: 0
150610 21:59:06 mysqld_safe mysqld restarted
150610 21:59:23 [Warning] '--default-character-set' is deprecated and will be removed in a future release.
Please use '--character-set-server' instead.
150610 21:59:24 InnoDB: Initializing buffer pool, size = 386.0M
150610 21:59:24 InnoDB: Error: cannot allocate 404766720 bytes of
InnoDB: memory with malloc! Total allocated memory
InnoDB: by InnoDB 7994352 bytes. Operating system errno: 12
InnoDB: Check if you should increase the swap file or
InnoDB: ulimits of your operating system.
注：このサーバのメモリは2GBです
23. InnoDB: ulimits of your operating system.
InnoDB: On FreeBSD check you have compiled the OS with
InnoDB: a big enough maximum process size.
InnoDB: Note that in most 32-bit computers the process
InnoDB: memory space is limited to 2 GB or 4 GB.
InnoDB: We keep retrying the allocation for 60 seconds...
150610 22:00:28InnoDB: Fatal error: cannot allocate the memory for the buffer pool
150610 22:00:28 [ERROR] Plugin 'InnoDB' init function returned error.
150610 22:00:29 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
150610 22:01:47 [Note] Event Scheduler: Loaded 0 events
150610 22:01:47 [Note] /usr/libexec/mysqld: ready for connections.
