{"id":1260,"date":"2018-02-16T11:30:05","date_gmt":"2018-02-16T09:30:05","guid":{"rendered":"http:\/\/www.ayhanarda.com\/blog\/?p=1260"},"modified":"2018-02-16T11:30:05","modified_gmt":"2018-02-16T09:30:05","slug":"tuning-primer-kurulumu-ve-kullanimi","status":"publish","type":"post","link":"https:\/\/www.ayhanarda.com\/blog\/2018\/02\/tuning-primer-kurulumu-ve-kullanimi\/","title":{"rendered":"Tuning Primer Kurulumu ve Kullan\u0131m\u0131"},"content":{"rendered":"

Tuning Primer Kurulumu ve Kullan\u0131m\u0131<\/h4>\n

Tuning Primer bir Mysql Tuner Alternatifi , a\u015fa\u011f\u0131daki komutlar\u0131 s\u0131ras\u0131 ile dosyas\u0131n\u0131 indirip \u00e7al\u0131\u015ft\u0131rabilirsiniz. Mysql Tuner kadar olmasada yeterli bilgiler mevcut ve kullanmaya de\u011fer.<\/p>\n

[root@ayhanarda ~]# cd \/usr\/local\/bin<\/strong><\/p>\n

[root@ayhanarda bin]# wget https:\/\/launchpadlibrarian.net\/78745738\/tuning-primer.sh<\/strong><\/p>\n

\u015eimdi s\u0131ra \u00e7al\u0131\u015ft\u0131rmaya geldi.<\/p>\n

[root@ayhanarda bin]# tuning-primer.sh<\/strong><\/p>\n

\u00c7al\u0131\u015ft\u0131r\u0131ld\u0131\u011f\u0131nda mysql in conf u ile elde etti\u011fi de\u011ferleri en iyi optimizasyon i\u00e7in kar\u015f\u0131la\u015ft\u0131rarak size \u00f6neriler sunuyor.<\/p>\n

Mysql in versiyonundan ne kadar s\u00fcredir servis verdi\u011fine , a\u00e7\u0131k oldu\u011fu son s\u00fcre i\u00e7inde ka\u00e7 query ye cevap verdi\u011fine, anl\u0131k ba\u011flant\u0131 say\u0131s\u0131na , slow query olup olmad\u0131\u011f\u0131na , cache size \u0131n\u0131z\u0131n yeterli olup olmad\u0131\u011f\u0131na , max connections de\u011ferinizin anl\u0131k de\u011ferinizi kar\u015f\u0131lay\u0131p kar\u015f\u0131lamad\u0131\u011f\u0131na , memory kullan\u0131m\u0131n\u0131za , join lerinize , temp alan\u0131n\u0131za , tablo lock say\u0131n\u0131za kadar \u00f6l\u00e7\u00fcp bi\u00e7ip size \u00f6neriler sunuyor. \u00d6rne\u011fin ben \u00e7aql\u0131\u015ft\u0131rd\u0131mda \u00e7\u0131kt\u0131s\u0131 a\u015fa\u011f\u0131daki gibi oldu.<\/p>\n

Ancak \u00f6ncesinde 48 saat kadar mysql servisinizin a\u00e7\u0131k olmas\u0131 daha do\u011fru sonu\u00e7lar alman\u0131z\u0131 sa\u011flayacakt\u0131r.<\/p>\n

MySQL Version 10.0.34-MariaDB x86_64<\/p>\n

Uptime = 1 days 18 hrs 21 min 54 sec
\nAvg. qps = 1402
\nTotal Questions = 213875408
\nThreads Connected = 34<\/p>\n

SLOW QUERIES
\nThe slow query log is NOT enabled.
\nCurrent long_query_time = 10.000000 sec.
\nYou have 8 out of 213875496 that take longer than 10.000000 sec. to complete
\nYour long_query_time seems to be fine<\/p>\n

WORKER THREADS
\nCurrent thread_cache_size = 200
\nCurrent threads_cached = 103
\nCurrent threads_per_sec = 0
\nHistoric threads_per_sec = 0
\nYour thread_cache_size is fine<\/p>\n

MAX CONNECTIONS
\nCurrent max_connections = 200
\nCurrent threads_connected = 35
\nHistoric max_used_connections = 137
\nThe number of used connections is 68% of the configured maximum.
\nYour max_connections variable seems to be fine.<\/p>\n

No InnoDB Support Enabled!<\/p>\n

MEMORY USAGE
\nMax Memory Ever Allocated : 13.54 G
\nConfigured Max Per-thread Buffers : 8.38 G
\nConfigured Max Global Buffers : 7.79 G
\nConfigured Max Memory Limit : 16.18 G
\nPhysical Memory : 23.36 G
\nMax memory limit seem to be within acceptable norms<\/p>\n

KEY BUFFER
\nCurrent MyISAM index space = 1.53 G
\nCurrent key_buffer_size = 1.00 G
\nKey cache miss rate is 1 : 99348
\nKey buffer free ratio = 54 %
\nYour key_buffer_size seems to be too high.
\nPerhaps you can use these resources elsewhere<\/p>\n

QUERY CACHE
\nQuery cache is enabled
\nCurrent query_cache_size = 800 M
\nCurrent query_cache_used = 800 M
\nCurrent query_cache_limit = 100 M
\nCurrent Query cache Memory fill ratio = 100.00 %
\nCurrent query_cache_min_res_unit = 4 K
\nMySQL won’t cache query results that are larger than query_cache_limit in size<\/p>\n

SORT OPERATIONS
\nCurrent sort_buffer_size = 1 M
\nCurrent read_rnd_buffer_size = 768 K
\nSort buffer seems to be fine<\/p>\n

JOINS
\n\/usr\/local\/bin\/tuning-primer.sh: line 402: export: `2097152′: not a valid identifier
\nCurrent join_buffer_size = 40.00 M
\nYou have had 576657 queries where a join could not use an index properly
\nYou have had 1303 joins without keys that check for key usage after each row
\njoin_buffer_size >= 4 M
\nThis is not advised
\nYou should enable “log-queries-not-using-indexes”
\nThen look for non indexed joins in the slow query log.<\/p>\n

OPEN FILES LIMIT
\nCurrent open_files_limit = 138451 files
\nThe open_files_limit should typically be set to at least 2x-3x
\nthat of table_cache if you have heavy MyISAM usage.
\nYour open_files_limit value seems to be fine<\/p>\n

TABLE CACHE
\nCurrent table_open_cache = 69120 tables
\nCurrent table_definition_cache = 65960 tables
\nYou have a total of 59378 tables
\nYou have 65487 open tables.
\nThe table_cache value seems to be fine<\/p>\n

TEMP TABLES
\nCurrent max_heap_table_size = 256 M
\nCurrent tmp_table_size = 1.46 G
\nOf 17855233 temp tables, 32% were created on disk
\nEffective in-memory tmp_table_size is limited to max_heap_table_size.
\nPerhaps you should increase your tmp_table_size and\/or max_heap_table_size
\nto reduce the number of disk-based temporary tables
\nNote! BLOB and TEXT columns are not allow in memory tables.
\nIf you are using these columns raising these values might not impact your
\nratio of on disk temp tables.<\/p>\n

TABLE SCANS
\nCurrent read_buffer_size = 1 M
\nCurrent table scan ratio = 309 : 1
\nread_buffer_size seems to be fine<\/p>\n

TABLE LOCKING
\nCurrent Lock Wait ratio = 1 : 1582
\nYou may benefit from selective use of InnoDB.
\nIf you have long running SELECT’s against MyISAM tables and perform
\nfrequent updates consider setting ‘low_priority_updates=1’<\/p>\n

Ayhan ARDA<\/p>\n

\"Share<\/a>