{"id":34902,"date":"2025-11-23T12:40:46","date_gmt":"2025-11-23T09:40:46","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=34902"},"modified":"2025-11-23T12:40:46","modified_gmt":"2025-11-23T09:40:46","slug":"mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/","title":{"rendered":"MySQL ve MariaDB&#8217;de Sorgular\u0131 ve Tablolar\u0131 Bir VPS \u00dczerinde Optimize Etme K\u0131lavuzu"},"content":{"rendered":"<p><body><\/p>\n<h2>MySQL ve MariaDB&#8217;de Sorgular\u0131 ve Tablolar\u0131 Bir VPS \u00dczerinde Optimize Etme K\u0131lavuzu<\/h2>\n<p>Bir Sanal \u00d6zel Sunucu (VPS) \u00fczerinde MySQL veya MariaDB \u00e7al\u0131\u015ft\u0131r\u0131rken, veritaban\u0131 performans\u0131n\u0131 optimize etmek, uygulaman\u0131z\u0131n h\u0131z\u0131, yan\u0131t verme s\u00fcresi ve genel kullan\u0131c\u0131 deneyimi i\u00e7in kritik \u00f6neme sahiptir. S\u0131n\u0131rl\u0131 kaynaklara sahip bir VPS ortam\u0131nda, her sorgunun ve her tablonun verimli \u00e7al\u0131\u015fmas\u0131, sunucu kaynaklar\u0131n\u0131n (CPU, RAM, Disk I\/O) en iyi \u015fekilde kullan\u0131lmas\u0131 anlam\u0131na gelir. Bu teknik makale, MySQL ve MariaDB veritabanlar\u0131n\u0131z\u0131 bir VPS \u00fczerinde optimize etmek i\u00e7in sorgu yaz\u0131m\u0131ndan tablo yap\u0131land\u0131rmas\u0131na, sunucu ayarlar\u0131ndan izleme ve bak\u0131ma kadar geni\u015f bir yelpazede stratejiler ve pratik ipu\u00e7lar\u0131 sunmaktad\u0131r.<\/p>\n<h2>Sorgu Optimizasyonunun Temelleri<\/h2>\n<p>Veritaban\u0131 performans\u0131n\u0131n en \u00f6nemli belirleyicilerinden biri, sorgular\u0131n ne kadar verimli \u00e7al\u0131\u015ft\u0131\u011f\u0131d\u0131r. K\u00f6t\u00fc yaz\u0131lm\u0131\u015f bir sorgu, do\u011fru indeksler olmasa bile t\u00fcm optimizasyon \u00e7abalar\u0131n\u0131z\u0131 bo\u015fa \u00e7\u0131karabilir.<\/p>\n<h3>EXPLAIN Kullan\u0131m\u0131<\/h3>\n<p><code>EXPLAIN<\/code> komutu, MySQL ve MariaDB&#8217;nin bir sorguyu nas\u0131l y\u00fcr\u00fctece\u011fini analiz etmenizi sa\u011flayan paha bi\u00e7ilmez bir ara\u00e7t\u0131r. Bir sorguyu <code>EXPLAIN<\/code> ile \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131n\u0131zda, veritaban\u0131 motorunun hangi tablolar\u0131 hangi s\u0131rayla tarad\u0131\u011f\u0131n\u0131, hangi indeksleri kulland\u0131\u011f\u0131n\u0131 veya kullanmad\u0131\u011f\u0131n\u0131 ve sorguyu tamamlamak i\u00e7in ne kadar i\u015f yapmas\u0131 gerekti\u011fini g\u00f6steren bir plan sunar.<\/p>\n<p><code>EXPLAIN SELECT * FROM users WHERE email = 'test@example.com';<\/code><\/p>\n<p><code>EXPLAIN<\/code> \u00e7\u0131kt\u0131s\u0131ndaki s\u00fctunlar \u015funlar\u0131 ifade eder:<br \/>\n*   <strong>id<\/strong>: Sorgu i\u00e7indeki select&#8217;lerin s\u0131ras\u0131.<br \/>\n*   <strong>select_type<\/strong>: Sorgu t\u00fcr\u00fc (SIMPLE, PRIMARY, SUBQUERY, UNION vb.).<br \/>\n*   <strong>table<\/strong>: \u0130\u015flem yap\u0131lan tablo.<br \/>\n*   <strong>partitions<\/strong>: Sorgunun etkiledi\u011fi b\u00f6l\u00fcmler (partitioning kullan\u0131l\u0131yorsa).<br \/>\n*   <strong>type<\/strong>: Eri\u015fim t\u00fcr\u00fc. Bu, en kritik s\u00fctunlardan biridir. <code>ALL<\/code> (tam tablo taramas\u0131) en k\u00f6t\u00fc, <code>index<\/code> (tam indeks taramas\u0131) daha iyi, <code>range<\/code> (indeks aral\u0131\u011f\u0131 taramas\u0131) iyi, <code>ref<\/code> (indeks anahtar\u0131 ile e\u015fle\u015fen t\u00fcm sat\u0131rlar) \u00e7ok iyi, <code>eq_ref<\/code> (birle\u015ftirme i\u00e7in tek bir sat\u0131r) m\u00fckemmel, <code>const<\/code> veya <code>system<\/code> (sabit de\u011ferler) en iyisidir. Hedefiniz genellikle <code>ref<\/code>, <code>eq_ref<\/code>, <code>const<\/code> veya <code>range<\/code> olmal\u0131d\u0131r.<br \/>\n*   <strong>possible_keys<\/strong>: Veritaban\u0131n\u0131n sorgu i\u00e7in kullanmay\u0131 d\u00fc\u015f\u00fcnd\u00fc\u011f\u00fc indeksler.<br \/>\n*   <strong>key<\/strong>: Veritaban\u0131n\u0131n ger\u00e7ekten kulland\u0131\u011f\u0131 indeks.<br \/>\n*   <strong>key_len<\/strong>: Kullan\u0131lan indeksin uzunlu\u011fu.<br \/>\n*   <strong>ref<\/strong>: Hangi s\u00fctunlar\u0131n veya sabitlerin <code>key<\/code> ile kar\u015f\u0131la\u015ft\u0131r\u0131ld\u0131\u011f\u0131n\u0131 g\u00f6sterir.<br \/>\n*   <strong>rows<\/strong>: Veritaban\u0131n\u0131n sorguyu \u00e7al\u0131\u015ft\u0131rmak i\u00e7in taramas\u0131 gerekti\u011fini tahmin etti\u011fi sat\u0131r say\u0131s\u0131. Ne kadar d\u00fc\u015f\u00fckse o kadar iyidir.<br \/>\n*   <strong>filtered<\/strong>: Tablo ko\u015fulu taraf\u0131ndan filtrelenen sat\u0131rlar\u0131n tahmini y\u00fczdesi.<br \/>\n*   <strong>Extra<\/strong>: Veritaban\u0131n\u0131n sorguyu nas\u0131l i\u015fledi\u011fi hakk\u0131nda ek bilgiler (<code>Using filesort<\/code>, <code>Using temporary<\/code>, <code>Using index<\/code>, <code>Using where<\/code> vb.). <code>Using filesort<\/code> veya <code>Using temporary<\/code> genellikle performans sorunlar\u0131na i\u015faret eder. <code>Using index<\/code> ise bir &#8220;covering index&#8221; kullan\u0131ld\u0131\u011f\u0131n\u0131 ve verilerin do\u011frudan indeksten al\u0131nd\u0131\u011f\u0131n\u0131 g\u00f6sterir, bu da \u00e7ok verimlidir.<\/p>\n<h3>\u0130ndekslerin Do\u011fru Kullan\u0131m\u0131<\/h3>\n<p>\u0130ndeksler, veritaban\u0131 tablolar\u0131ndaki verilere h\u0131zl\u0131 eri\u015fim sa\u011flamak i\u00e7in kullan\u0131lan \u00f6zel arama tablolar\u0131d\u0131r. T\u0131pk\u0131 bir kitab\u0131n i\u00e7indekiler veya dizin k\u0131sm\u0131 gibi \u00e7al\u0131\u015f\u0131r.<\/p>\n<p>*   <strong>Ne Zaman \u0130ndekslemeliyiz?<\/strong>:<br \/>\n    *   <code>WHERE<\/code> yan t\u00fcmcelerinde s\u0131k\u00e7a kullan\u0131lan s\u00fctunlar.<br \/>\n    *   <code>JOIN<\/code> ko\u015fullar\u0131nda kullan\u0131lan s\u00fctunlar.<br \/>\n    *   <code>ORDER BY<\/code> ve <code>GROUP BY<\/code> yan t\u00fcmcelerinde kullan\u0131lan s\u00fctunlar.<br \/>\n    *   <code>DISTINCT<\/code> veya <code>UNION<\/code> i\u015flemlerinde kullan\u0131lan s\u00fctunlar.<br \/>\n    *   Yabanc\u0131 anahtarlar (foreign keys) otomatik olarak indekslenir veya indekslenmeleri \u015fiddetle tavsiye edilir.<br \/>\n*   <strong>\u0130ndeks T\u00fcrleri<\/strong>:<br \/>\n    *   <strong>B-Tree (Varsay\u0131lan)<\/strong>: \u00c7o\u011fu durum i\u00e7in genel ama\u00e7l\u0131 indeks. E\u015fitlik, aral\u0131k ve s\u0131ralama sorgular\u0131 i\u00e7in etkilidir.<br \/>\n    *   <strong>Hash<\/strong>: Yaln\u0131zca e\u015fitlik kontrolleri i\u00e7in etkilidir. Memory depolama motoru tablolar\u0131nda kullan\u0131l\u0131r.<br \/>\n    *   <strong>Full-Text<\/strong>: Metin aramalar\u0131 i\u00e7in (LIKE ile aramalardan daha geli\u015fmi\u015f).<br \/>\n    *   <strong>Spatial<\/strong>: Co\u011frafi veriler i\u00e7in.<br \/>\n*   <strong>Tek S\u00fctunlu vs. Birle\u015fik (Composite) \u0130ndeksler<\/strong>:<br \/>\n    *   <strong>Tek S\u00fctunlu<\/strong>: Sadece bir s\u00fctunu indeksler. Basit <code>WHERE<\/code> ko\u015fullar\u0131 i\u00e7in iyidir.<br \/>\n    *   <strong>Birle\u015fik (Composite)<\/strong>: Birden fazla s\u00fctunu tek bir indekste birle\u015ftirir. S\u0131ra \u00f6nemlidir! \u00d6rne\u011fin, <code>(col1, col2, col3)<\/code> indeksinde, sorgu <code>col1<\/code>&#8216;i, <code>(col1, col2)<\/code>&#8216;yi veya <code>(col1, col2, col3)<\/code>&#8216;\u00fc kullanabilir, ancak sadece <code>col2<\/code>&#8216;yi veya <code>col3<\/code>&#8216;\u00fc kullanamaz.<br \/>\n*   <strong>\u0130ndekslerin Dezavantajlar\u0131<\/strong>:<br \/>\n    *   <strong>Depolama Alan\u0131<\/strong>: \u0130ndeksler diskte yer kaplar.<br \/>\n    *   <strong>Yazma Performans\u0131<\/strong>: <code>INSERT<\/code>, <code>UPDATE<\/code>, <code>DELETE<\/code> i\u015flemleri s\u0131ras\u0131nda indekslerin de g\u00fcncellenmesi gerekti\u011finden, yazma i\u015flemleri yava\u015flayabilir. Bu nedenle, gereksiz indekslerden ka\u00e7\u0131n\u0131lmal\u0131d\u0131r.<br \/>\n*   <strong>\u0130pu\u00e7lar\u0131<\/strong>:<br \/>\n    *   <code>USE INDEX<\/code>, <code>IGNORE INDEX<\/code>, <code>FORCE INDEX<\/code> hint&#8217;leri ile veritaban\u0131n\u0131n belirli bir indeksi kullanmas\u0131n\u0131 sa\u011flayabilir veya kullanmamas\u0131n\u0131 s\u00f6yleyebilirsiniz, ancak genellikle veritaban\u0131n\u0131n karar vermesine izin vermek en iyisidir.<\/p>\n<h3>Sorgu Yaz\u0131m Teknikleri<\/h3>\n<p>Sorgular\u0131n do\u011fru \u015fekilde yaz\u0131lmas\u0131, indekslerin etkin kullan\u0131m\u0131n\u0131 sa\u011flar ve veritaban\u0131 motorunun i\u015f y\u00fck\u00fcn\u00fc azalt\u0131r.<\/p>\n<p><em>   <strong><code>SELECT <\/em><\/code> Yerine Sadece Gerekli S\u00fctunlar\u0131 Se\u00e7in<\/strong>: Yaln\u0131zca ihtiyac\u0131n\u0131z olan s\u00fctunlar\u0131 se\u00e7mek, a\u011f trafi\u011fini azalt\u0131r, daha az bellek kullan\u0131r ve &#8220;covering index&#8221; kullan\u0131m\u0131na olanak tan\u0131r.<br \/>\n*   <strong><code>WHERE<\/code> Ko\u015fullar\u0131nda Fonksiyon Kullan\u0131m\u0131ndan Ka\u00e7\u0131n\u0131n<\/strong>: Bir s\u00fctuna fonksiyon uygulamak (\u00f6rn. <code>WHERE YEAR(date_column) = 2023<\/code>), veritaban\u0131n\u0131n o s\u00fctun \u00fczerindeki indeksi kullanmas\u0131n\u0131 engeller ve tam tablo taramas\u0131na yol a\u00e7ar. Bunun yerine, <code>WHERE date_column BETWEEN '2023-01-01' AND '2023-12-31'<\/code> gibi bir aral\u0131k sorgusu kullan\u0131n.<br \/>\n*   <strong><code>LIKE '%keyword'<\/code> Yerine <code>LIKE 'keyword%'<\/code> Kullan\u0131n<\/strong>: Ba\u015ftan arama (<code>keyword%<\/code>) indeksleri kullanabilirken, ortadan veya sondan arama (<code>%keyword%<\/code>, <code>%keyword<\/code>) genellikle indeksi kullanamaz.<br \/>\n*   <strong><code>JOIN<\/code> T\u00fcrlerini Do\u011fru Kullan\u0131n<\/strong>: <code>INNER JOIN<\/code>, <code>LEFT JOIN<\/code>, <code>RIGHT JOIN<\/code> aras\u0131ndaki farklar\u0131 anlay\u0131n ve sadece ihtiyac\u0131n\u0131z olan verileri birle\u015ftirmek i\u00e7in do\u011fru olan\u0131 kullan\u0131n. Gereksiz birle\u015ftirmelerden ka\u00e7\u0131n\u0131n.<br \/>\n*   <strong>Alt Sorgular (Subqueries) Yerine <code>JOIN<\/code> Kullan\u0131m\u0131<\/strong>: \u00c7o\u011fu durumda, <code>JOIN<\/code> i\u015flemleri e\u015fde\u011fer alt sorgulardan daha performansl\u0131d\u0131r, \u00f6zellikle b\u00fcy\u00fck veri k\u00fcmelerinde.<br \/>\n*   <strong><code>LIMIT<\/code> ve <code>OFFSET<\/code> ile Sayfalama Optimizasyonu<\/strong>: B\u00fcy\u00fck <code>OFFSET<\/code> de\u011ferleri performans sorunlar\u0131na yol a\u00e7abilir, \u00e7\u00fcnk\u00fc veritaban\u0131 sonu\u00e7 setinin ba\u015f\u0131na kadar olan t\u00fcm sat\u0131rlar\u0131 taramak zorunda kal\u0131r. M\u00fcmk\u00fcnse, son bilinen ID&#8217;yi kullanarak sayfalama yap\u0131n: <code>WHERE id > [last_id] ORDER BY id ASC LIMIT [page_size]<\/code>.<br \/>\n*   <strong><code>ORDER BY<\/code> ve <code>GROUP BY<\/code> \u0130\u00e7in \u0130ndeks Kullan\u0131m\u0131<\/strong>: <code>ORDER BY<\/code> veya <code>GROUP BY<\/code> yan t\u00fcmcelerinde kullan\u0131lan s\u00fctunlar \u00fczerinde indeksler olu\u015fturmak, <code>Using filesort<\/code> veya <code>Using temporary<\/code> i\u015flemlerini \u00f6nleyebilir. Birle\u015fik indekslerde s\u00fctunlar\u0131n s\u0131ras\u0131 burada da \u00f6nemlidir.<br \/>\n*   <strong><code>OR<\/code> Yerine <code>UNION ALL<\/code> Kullan\u0131m\u0131<\/strong>: Baz\u0131 karma\u015f\u0131k <code>OR<\/code> ko\u015fullar\u0131, \u00f6zellikle farkl\u0131 indeksleri hedefledi\u011finde, <code>UNION ALL<\/code> ile ayr\u0131 sorgulara b\u00f6l\u00fcnd\u00fc\u011f\u00fcnde daha iyi performans g\u00f6sterebilir.<br \/>\n*   <strong><code>HAVING<\/code> Yerine <code>WHERE<\/code> Kullan\u0131m\u0131<\/strong>: <code>HAVING<\/code> yan t\u00fcmcesi, <code>GROUP BY<\/code> i\u015fleminden sonra filtrelenirken, <code>WHERE<\/code> yan t\u00fcmcesi <code>GROUP BY<\/code> i\u015fleminden \u00f6nce filtreleme yapar. M\u00fcmk\u00fcnse, veriyi en erken a\u015famada filtrelemek i\u00e7in <code>WHERE<\/code> kullan\u0131n.<\/p>\n<h2>Tablo Yap\u0131s\u0131 Optimizasyonu<\/h2>\n<p>Veritaban\u0131 tablolar\u0131n\u0131n yap\u0131s\u0131, sorgu performans\u0131n\u0131 do\u011frudan etkiler. Do\u011fru veri tipleri, uygun normalizasyon seviyesi ve do\u011fru depolama motoru se\u00e7imi, performansta \u00f6nemli farklar yaratabilir.<\/p>\n<h3>Veri Tiplerinin Do\u011fru Se\u00e7imi<\/h3>\n<p>Her s\u00fctun i\u00e7in en uygun ve en k\u00fc\u00e7\u00fck veri tipini se\u00e7mek, disk alan\u0131ndan tasarruf etmenizi ve I\/O i\u015flemlerini azaltman\u0131z\u0131 sa\u011flar.<\/p>\n<p>*   <strong>Minimum Gerekli Veri Tipini Kullan\u0131n<\/strong>: \u00d6rne\u011fin, bir s\u00fctun sadece 1&#8217;den 100&#8217;e kadar de\u011ferler alacaksa <code>TINYINT<\/code> (0-255) kullan\u0131n, <code>INT<\/code> (yakla\u015f\u0131k 2 milyar) kullanmay\u0131n. Ayn\u0131 \u015fekilde, <code>VARCHAR(255)<\/code> yerine <code>VARCHAR(50)<\/code> yeterliyse, onu kullan\u0131n.<br \/>\n*   <strong>Sabit Uzunluklu (CHAR) vs. De\u011fi\u015fken Uzunluklu (VARCHAR)<\/strong>: <code>CHAR<\/code> sabit uzunluklu veriler i\u00e7in (\u00f6rn. \u00fclke kodlar\u0131), <code>VARCHAR<\/code> ise de\u011fi\u015fken uzunluklu veriler i\u00e7in daha iyidir. <code>VARCHAR<\/code> diskte daha az yer kaplar ancak veri uzunlu\u011fu de\u011fi\u015ftik\u00e7e fragmentation&#8217;a neden olabilir.<br \/>\n*   <strong>Say\u0131sal Veri Tipleri<\/strong>: <code>TINYINT<\/code>, <code>SMALLINT<\/code>, <code>MEDIUMINT<\/code>, <code>INT<\/code>, <code>BIGINT<\/code> gibi tipler aras\u0131nda ihtiyaca g\u00f6re se\u00e7im yap\u0131n. <code>UNSIGNED<\/code> kullanarak pozitif say\u0131lar i\u00e7in aral\u0131\u011f\u0131 ikiye katlayabilirsiniz.<br \/>\n*   <strong>Tarih ve Zaman Tipleri<\/strong>: <code>DATE<\/code>, <code>TIME<\/code>, <code>DATETIME<\/code>, <code>TIMESTAMP<\/code> gibi tipler aras\u0131nda do\u011fru se\u00e7imi yap\u0131n. <code>TIMESTAMP<\/code>, daha az yer kaplar ve zaman dilimi d\u00f6n\u00fc\u015f\u00fcmlerini otomatik yapar, ancak 2038 y\u0131l\u0131 s\u0131n\u0131rlamas\u0131 vard\u0131r. <code>DATETIME<\/code> daha geni\u015f bir aral\u0131\u011f\u0131 destekler.<br \/>\n*   <strong>ENUM ve SET<\/strong>: S\u0131n\u0131rl\u0131 ve bilinen de\u011fer listeleri i\u00e7in <code>ENUM<\/code> (tek se\u00e7im) veya <code>SET<\/code> (\u00e7oklu se\u00e7im) kullanmak, hem disk alan\u0131ndan tasarruf sa\u011flar hem de veri b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc art\u0131r\u0131r. Ancak, liste \u00e7ok s\u0131k de\u011fi\u015fiyorsa veya \u00e7ok uzunsa normalizasyon daha iyi bir se\u00e7enek olabilir.<\/p>\n<h3>Normalizasyon ve Denormalizasyon<\/h3>\n<p>Veritaban\u0131 tasar\u0131m\u0131nda normalizasyon ve denormalizasyon, performans ve veri b\u00fct\u00fcnl\u00fc\u011f\u00fc aras\u0131nda bir denge kurmay\u0131 gerektirir.<\/p>\n<p>*   <strong>Normalizasyon<\/strong>: Veri tekrar\u0131n\u0131 azaltmak ve veri b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc sa\u011flamak i\u00e7in veritaban\u0131 tablolar\u0131n\u0131 belirli kurallara g\u00f6re b\u00f6lme i\u015flemidir (\u00f6rn. 1NF, 2NF, 3NF).<br \/>\n    *   <strong>Avantajlar\u0131<\/strong>: Veri tekrar\u0131n\u0131 azalt\u0131r, veri b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc art\u0131r\u0131r, daha az depolama alan\u0131 gerektirir, <code>INSERT<\/code>, <code>UPDATE<\/code>, <code>DELETE<\/code> i\u015flemlerini basitle\u015ftirir.<br \/>\n    *   <strong>Dezavantajlar\u0131<\/strong>: Veri almak i\u00e7in daha fazla <code>JOIN<\/code> i\u015flemi gerektirir, bu da okuma sorgular\u0131n\u0131n performans\u0131n\u0131 d\u00fc\u015f\u00fcrebilir.<br \/>\n*   <strong>Denormalizasyon<\/strong>: Normalizasyon kurallar\u0131n\u0131 k\u0131smen ihlal ederek, performans\u0131 art\u0131rmak amac\u0131yla baz\u0131 verileri tekrar eden veya birle\u015ftiren bir i\u015flemdir.<br \/>\n    *   <strong>Avantajlar\u0131<\/strong>: <code>JOIN<\/code> ihtiyac\u0131n\u0131 azaltarak okuma sorgular\u0131n\u0131n performans\u0131n\u0131 art\u0131r\u0131r, raporlama sorgular\u0131 i\u00e7in idealdir.<br \/>\n    *   <strong>Dezavantajlar\u0131<\/strong>: Veri tekrar\u0131 artar, veri tutars\u0131zl\u0131\u011f\u0131 riski y\u00fckselir, <code>INSERT<\/code>, <code>UPDATE<\/code>, <code>DELETE<\/code> i\u015flemleri karma\u015f\u0131kla\u015f\u0131r.<br \/>\n*   <strong>Ne Zaman Denormalize Edilir?<\/strong>: Okuma a\u011f\u0131rl\u0131kl\u0131 uygulamalarda, s\u0131k\u00e7a eri\u015filen ve nadiren g\u00fcncellenen veriler i\u00e7in, veya karma\u015f\u0131k raporlama sorgular\u0131nda performans darbo\u011fazlar\u0131n\u0131 gidermek i\u00e7in denormalizasyon d\u00fc\u015f\u00fcn\u00fclebilir. Ancak bu, dikkatli planlama ve veri b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc koruma stratejileri gerektirir.<\/p>\n<h3>Depolama Motorlar\u0131 (Storage Engines)<\/h3>\n<p>MySQL ve MariaDB, farkl\u0131 depolama motorlar\u0131n\u0131 destekler ve her birinin kendine \u00f6zg\u00fc avantajlar\u0131 ve dezavantajlar\u0131 vard\u0131r.<\/p>\n<p>*   <strong>InnoDB<\/strong>: MySQL ve MariaDB&#8217;nin varsay\u0131lan depolama motorudur.<br \/>\n    *   <strong>\u00d6zellikleri<\/strong>: ACID uyumlu (Atomicity, Consistency, Isolation, Durability), sat\u0131r seviyesi kilitleme, yabanc\u0131 anahtar k\u0131s\u0131tlamalar\u0131, i\u015flem (transaction) deste\u011fi, MVCC (Multi-Version Concurrency Control) ile y\u00fcksek e\u015fzamanl\u0131l\u0131k.<br \/>\n    *   <strong>Kullan\u0131m Alan\u0131<\/strong>: \u00c7o\u011fu modern uygulama i\u00e7in, \u00f6zellikle veri b\u00fct\u00fcnl\u00fc\u011f\u00fc ve i\u015flem gerektiren senaryolarda \u00f6nerilir. Y\u00fcksek yazma ve okuma y\u00fcklerini iyi y\u00f6netir.<br \/>\n*   <strong>MyISAM<\/strong>: Daha eski bir depolama motorudur.<br \/>\n    *   <strong>\u00d6zellikleri<\/strong>: Tablo seviyesi kilitleme (ayn\u0131 anda sadece bir yazma i\u015flemi), ACID uyumlu de\u011fil, tam metin arama deste\u011fi, daha h\u0131zl\u0131 okuma (baz\u0131 senaryolarda).<br \/>\n    *   <strong>Kullan\u0131m Alan\u0131<\/strong>: Genellikle \u00f6nerilmez. Sadece okuma a\u011f\u0131rl\u0131kl\u0131, eski sistemler veya tam metin arama gerektiren \u00f6zel durumlar i\u00e7in d\u00fc\u015f\u00fcn\u00fclebilir. Veri b\u00fct\u00fcnl\u00fc\u011f\u00fc kritik de\u011filse ve e\u015fzamanl\u0131 yazma ihtiyac\u0131 yoksa kullan\u0131labilir.<br \/>\n*   <strong>MEMORY (HEAP)<\/strong>: Verileri RAM&#8217;de saklar.<br \/>\n    *   <strong>\u00d6zellikleri<\/strong>: \u00c7ok h\u0131zl\u0131 eri\u015fim, ancak sunucu yeniden ba\u015flat\u0131ld\u0131\u011f\u0131nda veriler kaybolur (kal\u0131c\u0131 de\u011fil). Tablo seviyesi kilitleme.<br \/>\n    *   <strong>Kullan\u0131m Alan\u0131<\/strong>: Ge\u00e7ici tablolar, \u00f6nbellekleme veya h\u0131zl\u0131 eri\u015fim gerektiren ara sonu\u00e7lar i\u00e7in.<br \/>\n*   <strong>Hangi Motoru Ne Zaman Kullanmal\u0131?<\/strong>: Modern uygulamalar\u0131n \u00e7o\u011fu i\u00e7in InnoDB tercih edilmelidir. Performans, veri b\u00fct\u00fcnl\u00fc\u011f\u00fc ve g\u00fcvenilirlik a\u00e7\u0131s\u0131ndan en iyi genel \u00e7\u00f6z\u00fcm\u00fc sunar. Depolama motorunu tablo olu\u015ftururken <code>ENGINE=InnoDB<\/code> ile belirtebilirsiniz.<\/p>\n<h2>MySQL\/MariaDB Sunucu Ayarlar\u0131 ve Optimizasyonu<\/h2>\n<p>Veritaban\u0131 sunucusunun yap\u0131land\u0131rma dosyas\u0131 olan <code>my.cnf<\/code> (veya <code>my.ini<\/code> Windows&#8217;ta), MySQL\/MariaDB performans\u0131n\u0131 \u00f6nemli \u00f6l\u00e7\u00fcde etkileyen \u00e7e\u015fitli parametreler i\u00e7erir. Bir VPS&#8217;in s\u0131n\u0131rl\u0131 kaynaklar\u0131 g\u00f6z \u00f6n\u00fcne al\u0131nd\u0131\u011f\u0131nda, bu ayarlar\u0131n do\u011fru yap\u0131lmas\u0131 hayati \u00f6nem ta\u015f\u0131r.<\/p>\n<h3>my.cnf Dosyas\u0131 ve \u00d6nemli Parametreler<\/h3>\n<p><code>my.cnf<\/code> dosyas\u0131 genellikle <code>\/etc\/mysql\/my.cnf<\/code>, <code>\/etc\/my.cnf<\/code> veya <code>\/etc\/mysql\/conf.d\/<\/code> dizinlerinde bulunur.<\/p>\n<p>*   <strong><code>innodb_buffer_pool_size<\/code><\/strong>: <strong>En kritik ayar.<\/strong> InnoDB motorunun verileri ve indeksleri \u00f6nbelle\u011fe almak i\u00e7in kulland\u0131\u011f\u0131 RAM miktar\u0131d\u0131r. Bu boyut ne kadar b\u00fcy\u00fck olursa, diske o kadar az eri\u015fim olur ve performans o kadar artar. Genellikle VPS&#8217;teki toplam RAM&#8217;in %50-80&#8217;i aral\u0131\u011f\u0131nda ayarlanmas\u0131 \u00f6nerilir (\u00f6rne\u011fin, 4GB RAM&#8217;li bir VPS i\u00e7in 2GB veya 3GB). Ancak, di\u011fer servislerin (web sunucusu, PHP-FPM vb.) de RAM&#8217;e ihtiyac\u0131 oldu\u011funu unutmay\u0131n.<br \/>\n*   <strong><code>key_buffer_size<\/code><\/strong>: MyISAM tablolar\u0131n\u0131n indekslerini \u00f6nbelle\u011fe almak i\u00e7in kullan\u0131l\u0131r. InnoDB kullan\u0131yorsan\u0131z \u00f6nemi d\u00fc\u015f\u00fckt\u00fcr.<br \/>\n*   <strong><code>query_cache_size<\/code><\/strong>: Sorgu \u00f6nbelle\u011fi. MySQL 5.7.20&#8217;den itibaren kullan\u0131mdan kald\u0131r\u0131ld\u0131 ve MySQL 8.0&#8217;da tamamen kald\u0131r\u0131ld\u0131. MariaDB&#8217;de hala mevcut olsa da, genellikle y\u00fcksek e\u015fzamanl\u0131l\u0131kta performans sorunlar\u0131na yol a\u00e7t\u0131\u011f\u0131 i\u00e7in kapat\u0131lmas\u0131 (<code>query_cache_size = 0<\/code>, <code>query_cache_type = 0<\/code>) veya \u00e7ok dikkatli kullan\u0131lmas\u0131 \u00f6nerilir. Modern veritabanlar\u0131, sorgu planlama ve di\u011fer \u00f6nbellekleme mekanizmalar\u0131 ile daha iyi performans g\u00f6sterir.<br \/>\n*   <strong><code>max_connections<\/code><\/strong>: Sunucuya ayn\u0131 anda ba\u011flanabilecek maksimum istemci say\u0131s\u0131. \u00c7ok y\u00fcksek de\u011ferler bellek t\u00fcketimini art\u0131rabilir ve sunucuyu yava\u015flatabilir. \u0130htiyac\u0131n\u0131za g\u00f6re ayarlay\u0131n, ancak a\u015f\u0131r\u0131ya ka\u00e7may\u0131n.<br \/>\n*   <strong><code>tmp_table_size<\/code> ve <code>max_heap_table_size<\/code><\/strong>: Bellekte olu\u015fturulabilecek ge\u00e7ici tablolar\u0131n maksimum boyutu. E\u011fer bir sorgu bu boyutlar\u0131 a\u015fan ge\u00e7ici bir tabloya ihtiya\u00e7 duyarsa, tablo diske yaz\u0131l\u0131r ve bu da performans\u0131 d\u00fc\u015f\u00fcr\u00fcr. <code>Created_tmp_disk_tables<\/code> durum de\u011fi\u015fkenini izleyerek bu de\u011ferleri ayarlayabilirsiniz. Genellikle ikisi de ayn\u0131 de\u011fere ayarlan\u0131r.<br \/>\n*   <strong><code>join_buffer_size<\/code><\/strong>: Tam tarama gerektiren birle\u015ftirmeler i\u00e7in kullan\u0131lan arabellek boyutu. Her bir <code>JOIN<\/code> i\u015flemi i\u00e7in ayr\u0131l\u0131r.<br \/>\n*   <strong><code>sort_buffer_size<\/code><\/strong>: <code>ORDER BY<\/code> veya <code>GROUP BY<\/code> i\u015flemleri s\u0131ras\u0131nda s\u0131ralama i\u00e7in kullan\u0131lan arabellek boyutu. Her oturum i\u00e7in ayr\u0131l\u0131r.<br \/>\n*   <strong><code>read_buffer_size<\/code><\/strong>: S\u0131ral\u0131 okuma i\u015flemleri i\u00e7in kullan\u0131lan arabellek.<br \/>\n*   <strong><code>read_rnd_buffer_size<\/code><\/strong>: Rastgele okuma i\u015flemleri i\u00e7in kullan\u0131lan arabellek.<br \/>\n*   <strong><code>expire_logs_days<\/code><\/strong>: Binary log dosyalar\u0131n\u0131n ka\u00e7 g\u00fcn saklanaca\u011f\u0131n\u0131 belirler. Yedekleme ve replikasyon i\u00e7in \u00f6nemlidir. Disk alan\u0131n\u0131z\u0131 d\u00fc\u015f\u00fcnerek ayarlay\u0131n.<br \/>\n*   <strong><code>slow_query_log<\/code> ve <code>long_query_time<\/code><\/strong>: Yava\u015f sorgu logunu etkinle\u015ftirir ve bir sorgunun yava\u015f kabul edilmesi i\u00e7in gereken s\u00fcreyi (saniye cinsinden) belirler. Optimizasyon i\u00e7in olmazsa olmaz bir ara\u00e7t\u0131r.<\/p>\n<h3>VPS Kaynak Y\u00f6netimi<\/h3>\n<p>VPS \u00fczerindeki fiziksel kaynaklar\u0131n do\u011fru y\u00f6netimi, veritaban\u0131 performans\u0131n\u0131 do\u011frudan etkiler.<\/p>\n<p>*   <strong>RAM<\/strong>: <code>innodb_buffer_pool_size<\/code> ayar\u0131 ile RAM&#8217;in b\u00fcy\u00fck bir k\u0131sm\u0131n\u0131 veritaban\u0131na tahsis etmek \u00f6nemlidir. Ancak, VPS&#8217;inizdeki di\u011fer servislerin de RAM&#8217;e ihtiyac\u0131 oldu\u011funu unutmay\u0131n. A\u015f\u0131r\u0131 tahsis, sistemin swap kullanmas\u0131na neden olabilir ki bu da performans\u0131 ciddi \u015fekilde d\u00fc\u015f\u00fcr\u00fcr.<br \/>\n*   <strong>CPU<\/strong>: Yo\u011fun sorgular veya y\u00fcksek e\u015fzamanl\u0131l\u0131k durumunda CPU darbo\u011faz\u0131 ya\u015fanabilir. <code>SHOW PROCESSLIST<\/code> ile \u00e7al\u0131\u015fan sorgular\u0131 kontrol edin.<br \/>\n*   <strong>Disk I\/O<\/strong>: Veritaban\u0131, \u00f6zellikle yazma yo\u011fun i\u015flemlerde veya \u00f6nbellekte olmayan verilere eri\u015firken diske s\u0131k\u00e7a ba\u015fvurur. <strong>SSD diskler, geleneksel HDD&#8217;lere g\u00f6re kat kat daha h\u0131zl\u0131 I\/O performans\u0131 sunar ve veritaban\u0131 i\u00e7in \u015fiddetle tavsiye edilir.<\/strong> Swap kullan\u0131m\u0131ndan ka\u00e7\u0131nmak i\u00e7in yeterli RAM&#8217;e sahip olmak da disk I\/O&#8217;yu azalt\u0131r.<\/p>\n<h2>\u0130zleme ve Bak\u0131m<\/h2>\n<p>Optimizasyon tek seferlik bir i\u015flem de\u011fildir; s\u00fcrekli izleme ve periyodik bak\u0131m gerektirir.<\/p>\n<h3>Yava\u015f Sorgu Loglar\u0131 (Slow Query Log)<\/h3>\n<p>Yava\u015f sorgu loglar\u0131, belirli bir s\u00fcrenin \u00fczerinde \u00e7al\u0131\u015fan sorgular\u0131 kaydeder. Bu, performans darbo\u011fazlar\u0131n\u0131 tespit etmenin en etkili yollar\u0131ndan biridir.<\/p>\n<p>*   <strong>Etkinle\u015ftirme<\/strong>: <code>my.cnf<\/code> dosyan\u0131za a\u015fa\u011f\u0131daki sat\u0131rlar\u0131 ekleyerek etkinle\u015ftirebilirsiniz:<\/p>\n<pre><code class=\"language-\">slow_query_log = 1\n    slow_query_log_file = \/var\/log\/mysql\/mysql-slow.log\n    long_query_time = 1\n    log_queries_not_using_indexes = 1  # \u0130ndeks kullanmayan sorgular\u0131 da logla<\/code><\/pre>\n<p>    Ard\u0131ndan MySQL\/MariaDB servisini yeniden ba\u015flat\u0131n.<br \/>\n*   <strong>Analiz<\/strong>: Log dosyas\u0131n\u0131 manuel olarak inceleyebilir veya <code>mysqldumpslow<\/code> gibi ara\u00e7lar\u0131 kullanabilirsiniz. Percona Toolkit&#8217;in <code>pt-query-digest<\/code> arac\u0131, yava\u015f sorgu loglar\u0131n\u0131 analiz etmek i\u00e7in \u00e7ok daha geli\u015fmi\u015f ve detayl\u0131 bir rapor sunar. Bu ara\u00e7lar, en yava\u015f sorgular\u0131, en s\u0131k \u00e7al\u0131\u015fan sorgular\u0131 ve bunlar\u0131n performans \u00fczerindeki etkilerini belirlemenize yard\u0131mc\u0131 olur.<\/p>\n<h3>Durum De\u011fi\u015fkenleri ve Metrikler<\/h3>\n<p>MySQL ve MariaDB, sunucunun mevcut durumu hakk\u0131nda bilgi sa\u011flayan bir\u00e7ok durum de\u011fi\u015fkeni ve metrik sunar.<\/p>\n<p>*   <strong><code>SHOW STATUS<\/code><\/strong>: Sunucunun genel durumu hakk\u0131nda bilgi verir.<br \/>\n*   <strong><code>SHOW VARIABLES<\/code><\/strong>: Sunucunun yap\u0131land\u0131rma de\u011fi\u015fkenlerini g\u00f6sterir.<br \/>\n*   <strong>\u00d6nemli Metrikler<\/strong>:<br \/>\n    *   <code>Innodb_buffer_pool_read_requests<\/code> ve <code>Innodb_buffer_pool_reads<\/code>: Buffer pool hit oran\u0131n\u0131 g\u00f6sterir. <code>Innodb_buffer_pool_reads<\/code> de\u011feri <code>Innodb_buffer_pool_read_requests<\/code> de\u011ferine g\u00f6re \u00e7ok d\u00fc\u015f\u00fck olmal\u0131d\u0131r. Y\u00fcksekse, buffer pool&#8217;unuzu b\u00fcy\u00fctmeniz gerekebilir.<br \/>\n    *   <code>Created_tmp_tables<\/code> ve <code>Created_tmp_disk_tables<\/code>: Bellekte ve diskte olu\u015fturulan ge\u00e7ici tablolar\u0131n say\u0131s\u0131. <code>Created_tmp_disk_tables<\/code> y\u00fcksekse, <code>tmp_table_size<\/code> ve <code>max_heap_table_size<\/code> de\u011ferlerini art\u0131rmay\u0131 d\u00fc\u015f\u00fcn\u00fcn.<br \/>\n    *   <code>Handler_read_rnd_next<\/code>: Tam tablo taramalar\u0131n\u0131n say\u0131s\u0131n\u0131 g\u00f6sterir. Y\u00fcksekse, indeksleme eksikli\u011fi olabilir.<br \/>\n    *   <code>Threads_connected<\/code>, <code>Threads_running<\/code>: Ba\u011fl\u0131 ve \u00e7al\u0131\u015fan i\u015f par\u00e7ac\u0131\u011f\u0131 say\u0131s\u0131. <code>Threads_running<\/code> y\u00fcksekse, darbo\u011faz olabilir.<br \/>\n    *   <code>Questions<\/code>: Sunucunun i\u015fledi\u011fi sorgu say\u0131s\u0131.<br \/>\n    *   <code>Uptime<\/code>: Sunucunun ne kadar s\u00fcredir \u00e7al\u0131\u015ft\u0131\u011f\u0131.<br \/>\n*   <strong>Monitoring Ara\u00e7lar\u0131<\/strong>: Bu metrikleri s\u00fcrekli izlemek i\u00e7in Prometheus\/Grafana, Zabbix veya Percona Monitoring and Management (PMM) gibi ara\u00e7lar\u0131 kullanmak, sorunlar\u0131 proaktif olarak tespit etmenizi sa\u011flar.<\/p>\n<h3>Periyodik Bak\u0131m<\/h3>\n<p>Veritaban\u0131 bak\u0131m\u0131, sa\u011fl\u0131kl\u0131 bir veritaban\u0131 ortam\u0131 i\u00e7in \u00f6nemlidir.<\/p>\n<p>*   <strong><code>OPTIMIZE TABLE<\/code><\/strong>: Tablolar\u0131 optimize eder. \u00d6zellikle MyISAM tablolar\u0131nda veri ve indeks fragmentasyonunu azalt\u0131r. InnoDB&#8217;de fragmentasyon daha az sorun te\u015fkil eder, \u00e7\u00fcnk\u00fc InnoDB verileri fiziksel olarak daha iyi d\u00fczenler. Ancak yine de b\u00fcy\u00fck silme ve g\u00fcncelleme i\u015flemlerinden sonra faydal\u0131 olabilir.<br \/>\n*   <strong><code>ANALYZE TABLE<\/code><\/strong>: Veritaban\u0131 motorunun sorgu planlay\u0131c\u0131s\u0131 taraf\u0131ndan kullan\u0131lan tablo istatistiklerini g\u00fcnceller. Bu, sorgu planlay\u0131c\u0131s\u0131n\u0131n en iyi y\u00fcr\u00fctme plan\u0131n\u0131 se\u00e7mesine yard\u0131mc\u0131 olur. \u00d6zellikle veri da\u011f\u0131l\u0131m\u0131 \u00f6nemli \u00f6l\u00e7\u00fcde de\u011fi\u015fti\u011finde \u00e7al\u0131\u015ft\u0131r\u0131lmal\u0131d\u0131r.<br \/>\n*   <strong>Veritaban\u0131 Yedeklemesi ve Restore Testi<\/strong>: Optimizasyon ne kadar \u00f6nemliyse, veri g\u00fcvenli\u011fi de o kadar \u00f6nemlidir. D\u00fczenli yedeklemeler al\u0131n ve bu yedekleri geri y\u00fckleyerek test edin.<\/p>\n<h2>Ek Optimizasyon \u0130pu\u00e7lar\u0131<\/h2>\n<p>Temel sorgu ve tablo optimizasyonlar\u0131n\u0131n \u00f6tesinde, uygulaman\u0131z\u0131n ve veritaban\u0131 mimarinizin genel performans\u0131n\u0131 art\u0131rabilecek ek stratejiler bulunmaktad\u0131r.<\/p>\n<h3>Veritaban\u0131 Ba\u011flant\u0131 Havuzlar\u0131 (Connection Pooling)<\/h3>\n<p>Her veritaban\u0131 ba\u011flant\u0131s\u0131, sunucu \u00fczerinde bir miktar kaynak (bellek, CPU) t\u00fcketir. Uygulaman\u0131z\u0131n her istek i\u00e7in yeni bir ba\u011flant\u0131 a\u00e7\u0131p kapatmas\u0131, performans d\u00fc\u015f\u00fc\u015f\u00fcne neden olabilir.<\/p>\n<p>*   <strong>Uygulama Katman\u0131 Ba\u011flant\u0131 Havuzlar\u0131<\/strong>: \u00c7o\u011fu modern programlama dili ve framework&#8217;\u00fc (\u00f6rn. Java JDBC, Python SQLAlchemy, Node.js Sequelize) yerle\u015fik ba\u011flant\u0131 havuzlama \u00f6zelliklerine sahiptir. Bu, mevcut ba\u011flant\u0131lar\u0131n yeniden kullan\u0131lmas\u0131n\u0131 sa\u011flayarak ba\u011flant\u0131 a\u00e7ma\/kapama maliyetini ortadan kald\u0131r\u0131r.<br \/>\n*   <strong>Veritaban\u0131 Proxy&#8217;leri<\/strong>: ProxySQL veya MaxScale gibi ara\u00e7lar, veritaban\u0131 sunucunuz ile uygulaman\u0131z aras\u0131na yerle\u015ferek ba\u011flant\u0131 havuzlama, y\u00fck dengeleme, okuma\/yazma ay\u0131rma ve sorgu y\u00f6nlendirme gibi geli\u015fmi\u015f \u00f6zellikler sunar. Bu, VPS&#8217;inizdeki tek bir veritaban\u0131 \u00f6rne\u011fi i\u00e7in bile ba\u011flant\u0131 y\u00f6netimini iyile\u015ftirebilir.<\/p>\n<h3>Replikasyon ve Y\u00fck Dengeleme<\/h3>\n<p>Uygulaman\u0131z\u0131n okuma y\u00fck\u00fc \u00e7ok y\u00fcksekse, tek bir veritaban\u0131 sunucusu darbo\u011faz haline gelebilir.<\/p>\n<p>*   <strong>Master-Slave Replikasyon<\/strong>: Bir Master sunucuya yazma i\u015flemleri yap\u0131l\u0131rken, Slave sunuculara okuma i\u015flemleri y\u00f6nlendirilebilir. Bu, okuma y\u00fck\u00fcn\u00fc da\u011f\u0131tarak performans\u0131 art\u0131r\u0131r. VPS ortam\u0131nda, ayr\u0131 bir VPS veya daha k\u00fc\u00e7\u00fck bir VPS kullanarak bir veya daha fazla Slave sunucu kurabilirsiniz.<br \/>\n*   <strong>Y\u00fcksek Eri\u015filebilirlik<\/strong>: Replikasyon ayn\u0131 zamanda bir Master sunucu ar\u0131zaland\u0131\u011f\u0131nda Slave sunuculardan birini yeni Master olarak atayarak y\u00fcksek eri\u015filebilirlik sa\u011flar.<br \/>\n*   <strong>Y\u00fck Dengeleme<\/strong>: ProxySQL veya MaxScale gibi ara\u00e7lar, gelen sorgular\u0131 otomatik olarak uygun Master veya Slave sunuculara y\u00f6nlendirerek y\u00fck dengeleme yapabilir.<\/p>\n<h3>Cache Mekanizmalar\u0131<\/h3>\n<p>Veritaban\u0131 \u00f6nbelle\u011fi (query cache) genellikle \u00f6nerilmese de, uygulama katman\u0131nda veya \u00f6zel \u00f6nbellekleme sistemleriyle veritaban\u0131 y\u00fck\u00fcn\u00fc azaltmak m\u00fcmk\u00fcnd\u00fcr.<\/p>\n<p>*   <strong>Uygulama Katman\u0131 Cache&#8217;leri<\/strong>: S\u0131k\u00e7a eri\u015filen ve nadiren de\u011fi\u015fen verileri uygulaman\u0131z\u0131n belle\u011finde veya Redis, Memcached gibi harici cache sistemlerinde saklay\u0131n. Bu, veritaban\u0131na yap\u0131lan sorgu say\u0131s\u0131n\u0131 \u00f6nemli \u00f6l\u00e7\u00fcde azalt\u0131r.<br \/>\n*   <strong>Tam Sayfa veya Par\u00e7al\u0131 Cache<\/strong>: Dinamik olarak olu\u015fturulan web sayfalar\u0131n\u0131 veya sayfa par\u00e7alar\u0131n\u0131 \u00f6nbelle\u011fe almak, veritaban\u0131 y\u00fck\u00fcn\u00fc b\u00fcy\u00fck \u00f6l\u00e7\u00fcde hafifletebilir.<\/p>\n<h2>Sonu\u00e7<\/h2>\n<p>MySQL ve MariaDB&#8217;de sorgu ve tablo optimizasyonu, \u00f6zellikle bir VPS gibi s\u0131n\u0131rl\u0131 kaynaklara sahip ortamlarda, uygulaman\u0131z\u0131n genel performans\u0131 ve s\u00fcrd\u00fcr\u00fclebilirli\u011fi i\u00e7in hayati \u00f6neme sahiptir. Bu makalede ele al\u0131nan stratejiler; <code>EXPLAIN<\/code> ile sorgu analizi, do\u011fru indeksleme, verimli sorgu yaz\u0131m teknikleri, uygun veri tipi ve depolama motoru se\u00e7imi, <code>my.cnf<\/code> dosyas\u0131ndaki sunucu ayarlar\u0131n\u0131n ince ayar\u0131, yava\u015f sorgu loglar\u0131n\u0131n izlenmesi ve periyodik bak\u0131m, birle\u015fik bir optimizasyon yakla\u015f\u0131m\u0131 sunar.<\/p>\n<p>Unutulmamal\u0131d\u0131r ki optimizasyon s\u00fcrekli bir s\u00fcre\u00e7tir. Uygulaman\u0131z b\u00fcy\u00fcd\u00fck\u00e7e, veri hacmi artt\u0131k\u00e7a ve kullan\u0131m senaryolar\u0131 de\u011fi\u015ftik\u00e7e, veritaban\u0131 performans\u0131n\u0131 s\u00fcrekli izlemek, analiz etmek ve ayarlamak gerekecektir. Her de\u011fi\u015fiklikten sonra performans\u0131 test etmek ve etkilerini \u00f6l\u00e7mek, do\u011fru kararlar\u0131 vermenizi sa\u011flayacakt\u0131r. Bu ad\u0131mlar\u0131 uygulayarak, VPS&#8217;inizdeki MySQL veya MariaDB veritaban\u0131n\u0131zdan en y\u00fcksek performans\u0131 alabilir ve uygulaman\u0131z\u0131n kullan\u0131c\u0131lar\u0131na sorunsuz bir deneyim sunabilirsiniz.<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"MySQL ve MariaDB&#8217;de Sorgular\u0131 ve Tablolar\u0131 Bir VPS \u00dczerinde Optimize Etme K\u0131lavuzu\nBir Sanal \u00d6zel Sunucu (VPS) \u00fczerinde MySQL veya MariaDB \u00e7al","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[138],"tags":[],"class_list":{"0":"post-34902","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-mysql","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v20.5 (Yoast SEO v25.3.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>MySQL ve MariaDB&#039;de Sorgular\u0131 ve Tablolar\u0131 Bir VPS \u00dczerinde Optimize Etme K\u0131lavuzu - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"MySQL ve MariaDB&#039;de Sorgular\u0131 ve Tablolar\u0131 Bir VPS \u00dczerinde Optimize Etme K\u0131lavuzu\" \/>\n<meta property=\"og:description\" content=\"MySQL ve MariaDB&#039;de Sorgular\u0131 ve Tablolar\u0131 Bir VPS \u00dczerinde Optimize Etme K\u0131lavuzu Bir Sanal \u00d6zel Sunucu (VPS) \u00fczerinde MySQL veya MariaDB \u00e7al\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-11-23T09:40:46+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"18 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"MySQL ve MariaDB&#8217;de Sorgular\u0131 ve Tablolar\u0131 Bir VPS \u00dczerinde Optimize Etme K\u0131lavuzu\",\"datePublished\":\"2025-11-23T09:40:46+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/\"},\"wordCount\":3358,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"MySQL\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/\",\"name\":\"MySQL ve MariaDB'de Sorgular\u0131 ve Tablolar\u0131 Bir VPS \u00dczerinde Optimize Etme K\u0131lavuzu - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-11-23T09:40:46+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"MySQL ve MariaDB&#8217;de Sorgular\u0131 ve Tablolar\u0131 Bir VPS \u00dczerinde Optimize Etme K\u0131lavuzu\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"MySQL ve MariaDB'de Sorgular\u0131 ve Tablolar\u0131 Bir VPS \u00dczerinde Optimize Etme K\u0131lavuzu - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/","og_locale":"tr_TR","og_type":"article","og_title":"MySQL ve MariaDB'de Sorgular\u0131 ve Tablolar\u0131 Bir VPS \u00dczerinde Optimize Etme K\u0131lavuzu","og_description":"MySQL ve MariaDB'de Sorgular\u0131 ve Tablolar\u0131 Bir VPS \u00dczerinde Optimize Etme K\u0131lavuzu Bir Sanal \u00d6zel Sunucu (VPS) \u00fczerinde MySQL veya MariaDB \u00e7al","og_url":"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-11-23T09:40:46+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"18 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"MySQL ve MariaDB&#8217;de Sorgular\u0131 ve Tablolar\u0131 Bir VPS \u00dczerinde Optimize Etme K\u0131lavuzu","datePublished":"2025-11-23T09:40:46+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/"},"wordCount":3358,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["MySQL"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/","url":"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/","name":"MySQL ve MariaDB'de Sorgular\u0131 ve Tablolar\u0131 Bir VPS \u00dczerinde Optimize Etme K\u0131lavuzu - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-11-23T09:40:46+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/mysql-ve-mariadbde-sorgulari-ve-tablolari-bir-vps-uzerinde-optimize-etme-kilavuzu\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"MySQL ve MariaDB&#8217;de Sorgular\u0131 ve Tablolar\u0131 Bir VPS \u00dczerinde Optimize Etme K\u0131lavuzu"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/34902","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=34902"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/34902\/revisions"}],"predecessor-version":[{"id":34903,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/34902\/revisions\/34903"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=34902"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=34902"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=34902"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}