2GB mem VPS에서 mysql을 최적화하기 위해 mysqltuner를 사용했고, 다음 권장 사항을 처리하는 방법을 이해하지 못했습니다. 특히 최대 메모리 사용량이 매우 높습니다., deal 이걸로? 누군가가 설명하도록 도울 수 있습니까? 감사.mysqltuner는 "MySQL의 최대 메모리 사용량이 위험 할 정도로 높습니다"는 것을 의미합니까?
-------- Performance Metrics -------------------------------------------------
[--] Up for: 3h 17m 7s (49K q [4.190 qps], 1K conn, TX: 70M, RX: 7M)
[--] Reads/Writes: 60%/40%
[--] Total buffers: 314.0M global + 6.4M per thread (300 max threads)
[!!] Maximum possible memory usage: 2.2G (119% of installed RAM)
[OK] Slow queries: 1% (785/49K)
[OK] Highest usage of available connections: 85% (256/300)
[!!] Cannot calculate MyISAM index size - re-run script as root user
[OK] Query cache efficiency: 92.4% (38K cached/41K selects)
[OK] Query cache prunes per day: 0
[OK] Sorts requiring temporary tables: 0% (0 temp sorts/633 sorts)
[!!] Temporary tables created on disk: 45% (315 on disk/699 total)
[OK] Thread cache hit rate: 74% (359 created/1K connections)
[OK] Table cache hit rate: 95% (141 open/148 opened)
[OK] Open file limit used: 12% (189/1K)
[OK] Table locks acquired immediately: 99% (6K immediate/6K locks)
-------- Recommendations -----------------------------------------------------
General recommendations:
Add skip-innodb to MySQL configuration to disable InnoDB
MySQL started within last 24 hours - recommendations may be inaccurate
Reduce your overall MySQL memory footprint for system stability
When making adjustments, make tmp_table_size/max_heap_table_size equal
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 ***
tmp_table_size (> 32M)
max_heap_table_size (> 32M)