Hallo Zusammen,
ich habe nun eine Frage zum MySQLTuner.
Ich habe schon alles möglich probiert, jedoch bekomme ich den join_buffer_size nicht weg...wie hoch soll/kann man den denn noch setzen?
Auch habe ich bereits die Tabellen optimiert - die Meldung, dass die Tabellen optimiert werden sollen, kommt jedoch nachwievor...
[--] Data in InnoDB tables: 4M (Tables: 271)
[--] Data in PERFORMANCE_SCHEMA tables: 0B (Tables: 17)
[!!] Total fragmented tables: 271
-------- Security Recommendations -------------------------------------------
[OK] All database users have passwords assigned
-------- Performance Metrics -------------------------------------------------
[--] Up for: 5m 7s (4K q [16.055 qps], 536 conn, TX: 979K, RX: 472K)
[--] Reads / Writes: 100% / 0%
[--] Total buffers: 4.5G global + 66.6M per thread (151 max threads)
[OK] Maximum possible memory usage: 14.3G (45% of installed RAM)
[OK] Slow queries: 0% (0/4K)
[OK] Highest usage of available connections: 3% (6/151)
[OK] Key buffer size / total MyISAM indexes: 4.0G/74.2M
[OK] Key buffer hit rate: 98.4% (137K cached / 2K reads)
[OK] Query cache efficiency: 64.8% (2K cached / 3K selects)
[OK] Query cache prunes per day: 0
[OK] Sorts requiring temporary tables: 0% (0 temp sorts / 502 sorts)
[!!] Joins performed without indexes: 7
[OK] Temporary tables created on disk: 9% (54 on disk / 586 total)
[OK] Thread cache hit rate: 98% (6 created / 536 connections)
[OK] Table cache hit rate: 23% (472 open / 1K opened)
[OK] Open file limit used: 4% (365/8K)
[OK] Table locks acquired immediately: 100% (1K immediate / 1K locks)
[OK] InnoDB data size / buffer pool: 4.6M/128.0M
-------- Recommendations -----------------------------------------------------
General recommendations:
Run OPTIMIZE TABLE to defragment tables for better performance
MySQL started within last 24 hours - recommendations may be inaccurate
Enable the slow query log to troubleshoot bad queries
Adjust your join queries to always utilize indexes
Variables to adjust:
join_buffer_size (> 64.0M, or always use indexes with joins)
ich habe nun eine Frage zum MySQLTuner.
Ich habe schon alles möglich probiert, jedoch bekomme ich den join_buffer_size nicht weg...wie hoch soll/kann man den denn noch setzen?
Auch habe ich bereits die Tabellen optimiert - die Meldung, dass die Tabellen optimiert werden sollen, kommt jedoch nachwievor...
[--] Data in InnoDB tables: 4M (Tables: 271)
[--] Data in PERFORMANCE_SCHEMA tables: 0B (Tables: 17)
[!!] Total fragmented tables: 271
-------- Security Recommendations -------------------------------------------
[OK] All database users have passwords assigned
-------- Performance Metrics -------------------------------------------------
[--] Up for: 5m 7s (4K q [16.055 qps], 536 conn, TX: 979K, RX: 472K)
[--] Reads / Writes: 100% / 0%
[--] Total buffers: 4.5G global + 66.6M per thread (151 max threads)
[OK] Maximum possible memory usage: 14.3G (45% of installed RAM)
[OK] Slow queries: 0% (0/4K)
[OK] Highest usage of available connections: 3% (6/151)
[OK] Key buffer size / total MyISAM indexes: 4.0G/74.2M
[OK] Key buffer hit rate: 98.4% (137K cached / 2K reads)
[OK] Query cache efficiency: 64.8% (2K cached / 3K selects)
[OK] Query cache prunes per day: 0
[OK] Sorts requiring temporary tables: 0% (0 temp sorts / 502 sorts)
[!!] Joins performed without indexes: 7
[OK] Temporary tables created on disk: 9% (54 on disk / 586 total)
[OK] Thread cache hit rate: 98% (6 created / 536 connections)
[OK] Table cache hit rate: 23% (472 open / 1K opened)
[OK] Open file limit used: 4% (365/8K)
[OK] Table locks acquired immediately: 100% (1K immediate / 1K locks)
[OK] InnoDB data size / buffer pool: 4.6M/128.0M
-------- Recommendations -----------------------------------------------------
General recommendations:
Run OPTIMIZE TABLE to defragment tables for better performance
MySQL started within last 24 hours - recommendations may be inaccurate
Enable the slow query log to troubleshoot bad queries
Adjust your join queries to always utilize indexes
Variables to adjust:
join_buffer_size (> 64.0M, or always use indexes with joins)
Kommentar