{"id":3586,"date":"2025-12-28T16:58:29","date_gmt":"2025-12-28T13:58:29","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/vpste-ram-swap-ve-oom-killer-yonetimi\/"},"modified":"2026-11-04T18:53:59","modified_gmt":"2026-11-04T15:53:59","slug":"vpste-ram-swap-ve-oom-killer-yonetimi","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/vpste-ram-swap-ve-oom-killer-yonetimi\/","title":{"rendered":"VPS\u2019te RAM, Swap ve OOM Killer Y\u00f6netimi"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div id=\"toc_container\" role=\"navigation\" aria-label=\"Table of Contents\" data-nosnippet class=\"toc_transparent no_bullets toc_numbered toc_title_center\"><p class=\"toc_title\">\u0130\u00e7indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#VPSte_Bellek_Yonetimi_Neden_Bu_Kadar_Onemli\"><span class=\"toc_number toc_depth_1\">1.<\/span> VPS\u2019te Bellek Y\u00f6netimi Neden Bu Kadar \u00d6nemli?<\/a><\/li><li><a href=\"#RAM_Swap_ve_Linux_Bellek_Modeli\"><span class=\"toc_number toc_depth_1\">2.<\/span> RAM, Swap ve Linux Bellek Modeli<\/a><ul><li><a href=\"#RAM_tam_olarak_neyi_tutar\"><span class=\"toc_number toc_depth_2\">2.1.<\/span> RAM tam olarak neyi tutar?<\/a><\/li><li><a href=\"#8220Dolu_RAM_her_zaman_sorundur8221_yanilgisi\"><span class=\"toc_number toc_depth_2\">2.2.<\/span> &#8220;Dolu RAM her zaman sorundur&#8221; yan\u0131lg\u0131s\u0131<\/a><\/li><li><a href=\"#Swap_nedir_gercekte_ne_ise_yarar\"><span class=\"toc_number toc_depth_2\">2.3.<\/span> Swap nedir, ger\u00e7ekte ne i\u015fe yarar?<\/a><\/li><\/ul><\/li><li><a href=\"#OOM_Killer_Nedir_Nasil_Calisir\"><span class=\"toc_number toc_depth_1\">3.<\/span> OOM Killer Nedir, Nas\u0131l \u00c7al\u0131\u015f\u0131r?<\/a><ul><li><a href=\"#OOM_Out_Of_Memory_durumu\"><span class=\"toc_number toc_depth_2\">3.1.<\/span> OOM (Out Of Memory) durumu<\/a><\/li><li><a href=\"#OOM_killer_hangi_sureci_oldurecegine_nasil_karar_verir\"><span class=\"toc_number toc_depth_2\">3.2.<\/span> OOM killer hangi s\u00fcreci \u00f6ld\u00fcrece\u011fine nas\u0131l karar verir?<\/a><\/li><li><a href=\"#OOM_loglarini_nerede_goruruz\"><span class=\"toc_number toc_depth_2\">3.3.<\/span> OOM log\u2019lar\u0131n\u0131 nerede g\u00f6r\u00fcr\u00fcz?<\/a><\/li><\/ul><\/li><li><a href=\"#VPSte_Bellek_Tasmasi_Senaryolari_Gercekci_Ornekler\"><span class=\"toc_number toc_depth_1\">4.<\/span> VPS\u2019te Bellek Ta\u015fmas\u0131 Senaryolar\u0131: Ger\u00e7ek\u00e7i \u00d6rnekler<\/a><ul><li><a href=\"#Senaryo_1_PHP-FPM_ve_WordPressWooCommerce\"><span class=\"toc_number toc_depth_2\">4.1.<\/span> Senaryo 1: PHP-FPM ve WordPress\/WooCommerce<\/a><\/li><li><a href=\"#Senaryo_2_PHP_memory_limit_ve_agir_rapor_isleri\"><span class=\"toc_number toc_depth_2\">4.2.<\/span> Senaryo 2: PHP memory_limit ve a\u011f\u0131r rapor i\u015fleri<\/a><\/li><li><a href=\"#Senaryo_3_MySQLPostgreSQL_buffer_ayarlari\"><span class=\"toc_number toc_depth_2\">4.3.<\/span> Senaryo 3: MySQL\/PostgreSQL buffer ayarlar\u0131<\/a><\/li><li><a href=\"#Senaryo_4_Izleme_log_ve_backup_surecleri\"><span class=\"toc_number toc_depth_2\">4.4.<\/span> Senaryo 4: \u0130zleme, log ve backup s\u00fcre\u00e7leri<\/a><\/li><\/ul><\/li><li><a href=\"#Adim_Adim_RAM_ve_Swap_Teshisi\"><span class=\"toc_number toc_depth_1\">5.<\/span> Ad\u0131m Ad\u0131m RAM ve Swap Te\u015fhisi<\/a><ul><li><a href=\"#free_tophtop_ve_proc_uzerinden_temel_analiz\"><span class=\"toc_number toc_depth_2\">5.1.<\/span> free, top\/htop ve \/proc \u00fczerinden temel analiz<\/a><\/li><li><a href=\"#Swap_kullanimini_dogru_okumak\"><span class=\"toc_number toc_depth_2\">5.2.<\/span> Swap kullan\u0131m\u0131n\u0131 do\u011fru okumak<\/a><\/li><li><a href=\"#Detayli_izleme_ve_alarmlar\"><span class=\"toc_number toc_depth_2\">5.3.<\/span> Detayl\u0131 izleme ve alarmlar<\/a><\/li><\/ul><\/li><li><a href=\"#Swap_Dosyasi_Olusturma_ve_Ayarlari\"><span class=\"toc_number toc_depth_1\">6.<\/span> Swap Dosyas\u0131 Olu\u015fturma ve Ayarlar\u0131<\/a><ul><li><a href=\"#Swap_boyutunu_nasil_secmeli\"><span class=\"toc_number toc_depth_2\">6.1.<\/span> Swap boyutunu nas\u0131l se\u00e7meli?<\/a><\/li><li><a href=\"#Swap_dosyasi_olusturma_ornegi\"><span class=\"toc_number toc_depth_2\">6.2.<\/span> Swap dosyas\u0131 olu\u015fturma \u00f6rne\u011fi<\/a><\/li><li><a href=\"#vmswappiness_ve_diger_kernel_ayarlari\"><span class=\"toc_number toc_depth_2\">6.3.<\/span> vm.swappiness ve di\u011fer kernel ayarlar\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#OOM_Killeri_Yonetmek_Onleme_Sinirlama_ve_Izleme\"><span class=\"toc_number toc_depth_1\">7.<\/span> OOM Killer\u2019\u0131 Y\u00f6netmek: \u00d6nleme, S\u0131n\u0131rlama ve \u0130zleme<\/a><ul><li><a href=\"#Overcommit_ayarlari\"><span class=\"toc_number toc_depth_2\">7.1.<\/span> Overcommit ayarlar\u0131<\/a><\/li><li><a href=\"#systemd_ile_servis_bazli_bellek_limitleri\"><span class=\"toc_number toc_depth_2\">7.2.<\/span> systemd ile servis bazl\u0131 bellek limitleri<\/a><\/li><li><a href=\"#OOM_scorer_ile_kritik_surecleri_korumak\"><span class=\"toc_number toc_depth_2\">7.3.<\/span> OOM scorer ile kritik s\u00fcre\u00e7leri korumak<\/a><\/li><\/ul><\/li><li><a href=\"#Uygulama_Tarafi_PHP_Nodejs_Java_ve_Digerleri\"><span class=\"toc_number toc_depth_1\">8.<\/span> Uygulama Taraf\u0131: PHP, Node.js, Java ve Di\u011ferleri<\/a><ul><li><a href=\"#PHP_ve_PHP-FPM_icin_pratik_oneriler\"><span class=\"toc_number toc_depth_2\">8.1.<\/span> PHP ve PHP-FPM i\u00e7in pratik \u00f6neriler<\/a><\/li><li><a href=\"#Nodejs_uygulamalari\"><span class=\"toc_number toc_depth_2\">8.2.<\/span> Node.js uygulamalar\u0131<\/a><\/li><li><a href=\"#Java_ve_JVM_tabanli_uygulamalar\"><span class=\"toc_number toc_depth_2\">8.3.<\/span> Java ve JVM tabanl\u0131 uygulamalar<\/a><\/li><\/ul><\/li><li><a href=\"#Kapasite_Planlama_ve_Onleyici_Stratejiler\"><span class=\"toc_number toc_depth_1\">9.<\/span> Kapasite Planlama ve \u00d6nleyici Stratejiler<\/a><ul><li><a href=\"#Baslangicta_dogru_VPS_boyutlandirmasi\"><span class=\"toc_number toc_depth_2\">9.1.<\/span> Ba\u015flang\u0131\u00e7ta do\u011fru VPS boyutland\u0131rmas\u0131<\/a><\/li><li><a href=\"#Periyodik_izleme_ve_trend_analizi\"><span class=\"toc_number toc_depth_2\">9.2.<\/span> Periyodik izleme ve trend analizi<\/a><\/li><li><a href=\"#Alarm_esigi_nasil_belirlenmeli\"><span class=\"toc_number toc_depth_2\">9.3.<\/span> Alarm e\u015fi\u011fi nas\u0131l belirlenmeli?<\/a><\/li><\/ul><\/li><li><a href=\"#Sonuc_VPSte_RAM_Swap_ve_OOM_Killeri_Rayina_Oturtmak\"><span class=\"toc_number toc_depth_1\">10.<\/span> Sonu\u00e7: VPS\u2019te RAM, Swap ve OOM Killer\u2019\u0131 Ray\u0131na Oturtmak<\/a><\/li><li><a href=\"#Birincil_Teknik_Kaynaklar\"><span class=\"toc_number toc_depth_1\">11.<\/span> Birincil Teknik Kaynaklar<\/a><\/li><\/ul><\/div>\n<h2><span id=\"VPSte_Bellek_Yonetimi_Neden_Bu_Kadar_Onemli\">VPS\u2019te Bellek Y\u00f6netimi Neden Bu Kadar \u00d6nemli?<\/span><\/h2>\n<p>Bir VPS\u2019te uygulama, veritaban\u0131 ve arka plan i\u015fleri ayn\u0131 bellek b\u00fct\u00e7esini payla\u015fabilir. PHP-FPM s\u00fcre\u00e7 say\u0131s\u0131, b\u00fcy\u00fck bir sorgu veya bellek ka\u00e7a\u011f\u0131 bu b\u00fct\u00e7eyi a\u015farsa gecikme, tahsis hatas\u0131 ya da beklenmedik servis duru\u015fu g\u00f6r\u00fclebilir. RAM dolulu\u011funu, aktif swap trafi\u011fini ve OOM olaylar\u0131n\u0131 birlikte incelemek, sorunun kapasiteden mi, bir s\u0131n\u0131rdan m\u0131 yoksa uygulama davran\u0131\u015f\u0131ndan m\u0131 kaynakland\u0131\u011f\u0131n\u0131 anlamaya yard\u0131mc\u0131 olur.<\/p>\n<p>Bu rehberde <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> \u00fczerinde <strong>RAM, swap ve OOM killer<\/strong> davran\u0131\u015f\u0131n\u0131; te\u015fhis, swap dosyas\u0131, <code>sysctl<\/code>, systemd\/cgroup limitleri ve uygulama b\u00fct\u00e7eleri \u00fczerinden ele al\u0131yoruz. \u00c7ekirdek davran\u0131\u015flar\u0131 i\u00e7in Linux 6.12, \u00f6rnek <code>free<\/code> hesab\u0131 i\u00e7in procps-ng 4.0.4 esas al\u0131nm\u0131\u015ft\u0131r; da\u011f\u0131t\u0131m\u0131n\u0131z\u0131n s\u00fcr\u00fcm ve yetki deste\u011fini kontrol edin. Yap\u0131land\u0131rma \u00f6rneklerini \u00f6nce ayr\u0131 test ortam\u0131nda do\u011frulay\u0131n; servis yeniden ba\u015flatma ve bellek s\u0131n\u0131r\u0131 de\u011fi\u015fiklikleri kesintiye neden olabilir.<\/p>\n<h2><span id=\"RAM_Swap_ve_Linux_Bellek_Modeli\">RAM, Swap ve Linux Bellek Modeli<\/span><\/h2>\n<h3><span id=\"RAM_tam_olarak_neyi_tutar\">RAM tam olarak neyi tutar?<\/span><\/h3>\n<p>RAM, s\u00fcre\u00e7lerin o anda yerle\u015fik olan kod ve verilerinin yan\u0131 s\u0131ra \u00e7ekirdek veri yap\u0131lar\u0131n\u0131, \u00f6nbellekleri ve tamponlar\u0131 tutar. Her ayr\u0131lm\u0131\u015f sanal adresin RAM\u2019de bir sayfas\u0131 bulunmas\u0131 gerekmez. <strong>Sanal bellek<\/strong>, uygulaman\u0131n g\u00f6rd\u00fc\u011f\u00fc adres alan\u0131 ve e\u015fleme d\u00fczenidir; RAM + swap toplam\u0131 de\u011fildir. E\u015flemeler dosyalarla desteklenebilir, payla\u015f\u0131ml\u0131 olabilir veya hen\u00fcz fiziksel sayfa ayr\u0131lmam\u0131\u015f alanlar i\u00e7erebilir.<\/p>\n<p>\u00d6zetle RAM\u2019de \u015funlar bulunur:<\/p>\n<ul>\n<li>\u00c7al\u0131\u015fan s\u00fcre\u00e7lerin kodu ve heap\/stack bellekleri<\/li>\n<li>Disk \u00f6nbelle\u011fi (page cache)<\/li>\n<li>Filesystem ve a\u011f buffer\u2019lar\u0131<\/li>\n<li>Kernel veri yap\u0131lar\u0131<\/li>\n<\/ul>\n<p>Bu y\u00fczden <code>free -h<\/code> \u00e7\u0131kt\u0131s\u0131nda RAM\u2019in dolu g\u00f6r\u00fcnmesi tek ba\u015f\u0131na sorun de\u011fildir. Yeni i\u015fler i\u00e7in kullan\u0131labilir bellek tahminini, geri kazan\u0131m etkinli\u011fini ve uygulama gecikmesini birlikte de\u011ferlendirin; doluluk ile bellek bask\u0131s\u0131 ayn\u0131 \u00f6l\u00e7\u00fcm de\u011fildir.<\/p>\n<h3><span id=\"8220Dolu_RAM_her_zaman_sorundur8221_yanilgisi\">&#8220;Dolu RAM her zaman sorundur&#8221; yan\u0131lg\u0131s\u0131<\/span><\/h3>\n<p>Linux\u2019ta ama\u00e7 RAM\u2019i bo\u015f tutmak de\u011fil, <strong>verimli kullanmakt\u0131r<\/strong>. <code>available<\/code>, yeni uygulamalar i\u00e7in swap yapmadan kullan\u0131labilecek belle\u011fin tahminidir; \u00f6nbelle\u011fin tamam\u0131 an\u0131nda geri al\u0131namaz. Kirli dosya sayfalar\u0131n\u0131n \u00f6nce diske yaz\u0131lmas\u0131 gerekebilir. <em>used<\/em> alan\u0131n\u0131n y\u00fcksek olmas\u0131 tek ba\u015f\u0131na ne bellek sorunu oldu\u011funu ne de sistemin iyi \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 g\u00f6sterir; <em>available<\/em> ve <em>buff\/cache<\/em> alanlar\u0131yla birlikte de\u011ferlendirilmelidir.<\/p>\n<p>\u0130zlerken <em>available<\/em> alan\u0131na dikkat edin. A\u015fa\u011f\u0131daki say\u0131lar \u00f6l\u00e7\u00fcm de\u011fil, <strong>procps-ng 4.0.4 i\u00e7in MiB cinsinden temsili bir \u00e7\u0131kt\u0131<\/strong> \u00f6rne\u011fidir. <code>free --version<\/code> ile s\u00fcr\u00fcm\u00fc kontrol edin; <code>free -h<\/code> birimleri otomatik se\u00e7er, <code>free -m<\/code> ise MiB g\u00f6sterir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">free -m\n              total        used        free      shared  buff\/cache   available\nMem:           4096        3072         256          64        1536        1024\nSwap:          2048         128        1920\n<\/code><\/pre>\n<p>Bu s\u00fcr\u00fcmde RAM i\u00e7in <strong>used = total \u2212 available<\/strong>: 4096 \u2212 1024 = 3072 MiB. Bu nedenle <code>used + free + buff\/cache<\/code> toplam\u0131n\u0131 <code>total<\/code> ile e\u015fitlemeyin; <code>shared<\/code> da ayr\u0131ca toplanacak ba\u011f\u0131ms\u0131z bir kalem de\u011fildir. 1024 MiB <code>available<\/code>, o andaki tahmini hareket alan\u0131d\u0131r; sonraki taleplerin kar\u015f\u0131lanaca\u011f\u0131n\u0131 veya bir cgroup s\u0131n\u0131r\u0131 nedeniyle OOM ya\u015fanmayaca\u011f\u0131n\u0131 garanti etmez. Eski procps s\u00fcr\u00fcmleri farkl\u0131 <code>used<\/code> hesab\u0131 yapabilir.<\/p>\n<h3><span id=\"Swap_nedir_gercekte_ne_ise_yarar\">Swap nedir, ger\u00e7ekte ne i\u015fe yarar?<\/span><\/h3>\n<p>Swap, uygun bellek sayfalar\u0131n\u0131n RAM d\u0131\u015f\u0131nda saklanabildi\u011fi aland\u0131r. Bu rehberde disk \u00fczerindeki swap dosyas\u0131 ele al\u0131n\u0131yor; zram gibi s\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f RAM tabanl\u0131 d\u00fczenler farkl\u0131d\u0131r. Swap, yaln\u0131zca b\u00fct\u00fcn RAM bittikten sonra kullan\u0131lan bir son ad\u0131m de\u011fildir: \u00e7ekirdek bellek bask\u0131s\u0131 ve geri kazan\u0131m maliyetlerini de\u011ferlendirerek uygun sayfalar\u0131 daha \u00f6nce de d\u0131\u015far\u0131 ta\u015f\u0131yabilir.<\/p>\n<p>Swap\u2019in temel ama\u00e7lar\u0131:<\/p>\n<ul>\n<li>Uygun sayfalar\u0131 d\u0131\u015far\u0131 ta\u015f\u0131yarak baz\u0131 k\u0131sa s\u00fcreli talep art\u0131\u015flar\u0131nda kapasite pay\u0131 olu\u015fturmak<\/li>\n<li>Daha az kullan\u0131lan swap destekli sayfalar\u0131n yerini aktif i\u015flere veya yararl\u0131 dosya \u00f6nbelle\u011fine b\u0131rakabilmek<\/li>\n<li>Baz\u0131 i\u015f y\u00fcklerinde OOM riskini azaltmak; cgroup\/ay\u0131rma s\u0131n\u0131rlar\u0131n\u0131 veya t\u00fcm OOM nedenlerini ortadan kald\u0131rd\u0131\u011f\u0131n\u0131 varsaymamak<\/li>\n<\/ul>\n<p>Disk tabanl\u0131 swap\u2019in etkisi, depolama gecikmesine, ayn\u0131 diskteki di\u011fer I\/O y\u00fck\u00fcne ve aktif \u00e7al\u0131\u015fma k\u00fcmesinin b\u00fcy\u00fckl\u00fc\u011f\u00fcne ba\u011fl\u0131d\u0131r. NVMe etiketi tek ba\u015f\u0131na kabul edilebilir uygulama performans\u0131n\u0131 kan\u0131tlamaz. <strong>Swap, yeterli RAM\u2019in yerini tutmaz<\/strong>; yo\u011fun swap giri\u015f \u00e7\u0131k\u0131\u015f\u0131 sitenizi yava\u015flatabilir. Swap olmamas\u0131 tek ba\u015f\u0131na \u00e7\u00f6kme nedeni de\u011fildir; risk, i\u015f y\u00fck\u00fcn\u00fcn bellek ihtiyac\u0131 ile kullan\u0131labilir kapasiteye ba\u011fl\u0131d\u0131r.<\/p>\n<h2><span id=\"OOM_Killer_Nedir_Nasil_Calisir\">OOM Killer Nedir, Nas\u0131l \u00c7al\u0131\u015f\u0131r?<\/span><\/h2>\n<h3><span id=\"OOM_Out_Of_Memory_durumu\">OOM (Out Of Memory) durumu<\/span><\/h3>\n<p>\u00c7ekirdek, belirli bir bellek tahsisini ilgili k\u0131s\u0131tlar i\u00e7inde kar\u015f\u0131layamad\u0131\u011f\u0131nda ve yeterli geri kazan\u0131m yap\u0131lamad\u0131\u011f\u0131nda OOM yoluna girebilir. Bunun i\u00e7in sistemdeki b\u00fct\u00fcn RAM ve swap\u2019in bitmesi gerekmez: cgroup bellek s\u0131n\u0131r\u0131, izin verilen NUMA d\u00fc\u011f\u00fcmleri veya cpuset\/memory policy gibi k\u0131s\u0131tlar \u00f6nemlidir. Bellek cgroup OOM\u2019u ilgili grubun adaylar\u0131yla s\u0131n\u0131rl\u0131d\u0131r. Baz\u0131 tahsisler ise OOM kill yerine hata d\u00f6nebilir; her bellek hatas\u0131 bir s\u00fcre\u00e7 \u00f6ld\u00fcr\u00fcld\u00fc\u011f\u00fc anlam\u0131na gelmez.<\/p>\n<p>Bellek bask\u0131s\u0131 veya cgroup s\u0131n\u0131r\u0131na ula\u015fma a\u00e7\u0131s\u0131ndan incelenebilecek \u00f6rnekler:<\/p>\n<ul>\n<li>PHP-FPM havuzunda \u00e7ok fazla child process a\u00e7\u0131lmas\u0131<\/li>\n<li>Node.js veya Java uygulamas\u0131nda bellek ka\u00e7a\u011f\u0131<\/li>\n<li>MySQL\/PostgreSQL buffer ve cache ayarlar\u0131n\u0131n a\u015f\u0131r\u0131 agresif olmas\u0131<\/li>\n<li>Arka plan kuyruk i\u015f\u00e7ilerinin (queue workers) s\u0131n\u0131rs\u0131z \u00e7o\u011falmas\u0131<\/li>\n<\/ul>\n<h3><span id=\"OOM_killer_hangi_sureci_oldurecegine_nasil_karar_verir\">OOM killer hangi s\u00fcreci \u00f6ld\u00fcrece\u011fine nas\u0131l karar verir?<\/span><\/h3>\n<p>Linux 6.12\u2019nin ola\u011fan kurban taramas\u0131nda, uygun aday\u0131n yerle\u015fik sayfalar\u0131 (RSS), swap girdileri ve sayfa tablolar\u0131 temel hesaba kat\u0131l\u0131r; <code>oom_score_adj<\/code> bu skoru de\u011fi\u015ftirir. Pozitif de\u011fer se\u00e7ilme e\u011filimini art\u0131r\u0131r, negatif de\u011fer azalt\u0131r; bu, CPU zamanlay\u0131c\u0131s\u0131n\u0131n <code>nice<\/code> \u00f6nceli\u011fi de\u011fildir. Root kullan\u0131c\u0131s\u0131 olmak veya servisin i\u015fletme a\u00e7\u0131s\u0131ndan \u00f6nemli olmas\u0131 bu s\u00fcr\u00fcm\u00fcn skor hesab\u0131nda ayr\u0131 bir otomatik koruma sa\u011flamaz.<\/p>\n<p>Tarama kapsam\u0131 ve istisnalar vard\u0131r: global init, \u00e7ekirdek i\u015f par\u00e7ac\u0131klar\u0131 ve <code>oom_score_adj=-1000<\/code> ile d\u0131\u015flanan g\u00f6revler ola\u011fan aday de\u011fildir; cgroup\/NUMA k\u0131s\u0131tlar\u0131 aday k\u00fcmesini daraltabilir. \u00d6zel \u00e7ekirdek ayarlar\u0131 veya zaten sonlanmakta olan bir g\u00f6rev farkl\u0131 yollar\u0131 devreye sokabilir. Dolay\u0131s\u0131yla yaln\u0131zca en y\u00fcksek RSS\u2019ye ya da tek bir <code>\/proc\/PID\/oom_score<\/code> anl\u0131k de\u011ferine bakarak s\u0131radaki kurban\u0131 kesin belirleyemezsiniz. \u00d6ld\u00fcr\u00fclen s\u00fcre\u00e7, bellek bask\u0131s\u0131n\u0131n as\u0131l kayna\u011f\u0131 olmak zorunda de\u011fildir.<\/p>\n<p>\u00d6nce ger\u00e7ek s\u00fcre\u00e7 ad\u0131n\u0131 do\u011frulay\u0131n; PHP-FPM ad\u0131 da\u011f\u0131t\u0131ma g\u00f6re de\u011fi\u015febilir. Birden fazla PID varsa her birini ayr\u0131 inceleyin. A\u015fa\u011f\u0131daki <code>1234<\/code> \u00f6rne\u011fini ilgili s\u00fcrecin say\u0131sal PID de\u011feriyle de\u011fi\u015ftirin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">pidof php-fpm\npid=1234\ncat &quot;\/proc\/$pid\/oom_score&quot;\ncat &quot;\/proc\/$pid\/oom_score_adj&quot;\n<\/code><\/pre>\n<p>Kritik servislerin OOM taraf\u0131ndan \u00f6ld\u00fcr\u00fclme riskini azaltmak i\u00e7in skor ayar\u0131 yap\u0131labilir. \u00d6rne\u011fin veritaban\u0131 s\u00fcrecinin <code>oom_score_adj<\/code> de\u011ferini d\u00fc\u015f\u00fcrmek, se\u00e7ilme olas\u0131l\u0131\u011f\u0131n\u0131 azaltabilir; son \u00f6ld\u00fcr\u00fclecek s\u00fcre\u00e7 olaca\u011f\u0131n\u0131 garanti etmez ve bellek yetersizli\u011fini \u00e7\u00f6zmez.<\/p>\n<h3><span id=\"OOM_loglarini_nerede_goruruz\">OOM log\u2019lar\u0131n\u0131 nerede g\u00f6r\u00fcr\u00fcz?<\/span><\/h3>\n<p>OOM olaylar\u0131 genellikle kernel log\u2019lar\u0131na d\u00fc\u015fer. A\u015fa\u011f\u0131daki komutlarla eri\u015febildi\u011finiz kernel kay\u0131tlar\u0131nda OOM ile ilgili e\u015fle\u015fmeleri arayabilirsiniz; bu aramalar eksiksiz bir olay ge\u00e7mi\u015fi sunmaz:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">dmesg | grep -i oom\njournalctl -k | grep -i &quot;out of memory&quot;\n<\/code><\/pre>\n<p>E\u015fle\u015fen sat\u0131rlar OOM olay\u0131n\u0131 bulman\u0131za yard\u0131mc\u0131 olur. Hangi s\u00fcrecin \u00f6ld\u00fcr\u00fcld\u00fc\u011f\u00fcn\u00fc ve olay s\u0131ras\u0131ndaki bellek durumunu de\u011ferlendirmek i\u00e7in ayn\u0131 zaman aral\u0131\u011f\u0131ndaki \u00e7evreleyen kernel kay\u0131tlar\u0131n\u0131 da inceleyin; filtrelenmi\u015f \u00e7\u0131kt\u0131 t\u00fcm ayr\u0131nt\u0131lar\u0131 i\u00e7ermeyebilir. G\u00fcnl\u00fcklere eri\u015fim yetkisi ve saklama s\u00fcresi g\u00f6r\u00fcn\u00fcrl\u00fc\u011f\u00fc s\u0131n\u0131rlar. Kurban PID\u2019sini, tahsisi isteyen g\u00f6revi, cgroup yolunu ve servis metriklerini ili\u015fkilendirin; ayn\u0131 servis s\u00fcrekli \u00f6ld\u00fcr\u00fclse bile bunu tek ba\u015f\u0131na bellek ka\u00e7a\u011f\u0131 kan\u0131t\u0131 saymay\u0131n.<\/p>\n<p>Ayr\u0131ca etkinse <code>systemd-oomd<\/code>, cgroup v2 ve PSI \u00f6l\u00e7\u00fcmleriyle \u00e7ekirde\u011fin OOM an\u0131ndan \u00f6nce s\u00fcre\u00e7leri sonland\u0131rabilir. Bu durumda <code>journalctl -u systemd-oomd<\/code> ve ilgili servis g\u00fcnl\u00fckleri de incelenmelidir; yaln\u0131zca kernel OOM filtresi yeterli de\u011fildir.<\/p>\n<h2><span id=\"VPSte_Bellek_Tasmasi_Senaryolari_Gercekci_Ornekler\">VPS\u2019te Bellek Ta\u015fmas\u0131 Senaryolar\u0131: Ger\u00e7ek\u00e7i \u00d6rnekler<\/span><\/h2>\n<h3><span id=\"Senaryo_1_PHP-FPM_ve_WordPressWooCommerce\">Senaryo 1: PHP-FPM ve WordPress\/WooCommerce<\/span><\/h3>\n<p>WordPress veya WooCommerce \u00e7al\u0131\u015ft\u0131r\u0131lan varsay\u0131msal bir VPS\u2019te, PHP-FPM havuzundaki <strong>pm.max_children<\/strong> de\u011ferinin RAM\u2019e g\u00f6re fazla y\u00fcksek ayarland\u0131\u011f\u0131n\u0131 d\u00fc\u015f\u00fcnelim. Hesab\u0131 g\u00f6stermek i\u00e7in her child process\u2019in 60\u2013150 MB RAM t\u00fcketti\u011fini varsayarsak, 20 child process\u2019in toplam ihtiyac\u0131 kabaca 1,2\u20133 GB olur. Bu, di\u011fer servisler hesaba kat\u0131lmadan bile 2 GB RAM\u2019li bir VPS\u2019in kapasitesini a\u015fabilir. Bu aral\u0131k bir \u00f6l\u00e7\u00fcm veya genel \u00f6neri de\u011fildir; ger\u00e7ek boyutland\u0131rmada kendi i\u015f y\u00fck\u00fcn\u00fcz\u00fcn bellek t\u00fcketimini \u00f6l\u00e7\u00fcn ve payla\u015f\u0131lan belle\u011fi tekrar tekrar saymamaya dikkat edin.<\/p>\n<p>Bu konuyu detayl\u0131 i\u015fledi\u011fimiz <a href=\"https:\/\/www.dchost.com\/blog\/wordpress-ve-woocommerce-icin-php-fpm-ayarlari-pm-max-children\/\">WordPress ve WooCommerce i\u00e7in PHP-FPM ayarlar\u0131 rehberinde<\/a> her child\u2019\u0131n tahmini RAM t\u00fcketimi \u00fczerinden nas\u0131l hesap yap\u0131laca\u011f\u0131n\u0131 anlatt\u0131k. <code>pm.max_children<\/code> de\u011ferini bu hesab\u0131 yapmadan art\u0131rmak, e\u015fzamanl\u0131 bellek talebini b\u00fct\u00e7enin \u00fczerine \u00e7\u0131karabilir.<\/p>\n<h3><span id=\"Senaryo_2_PHP_memory_limit_ve_agir_rapor_isleri\">Senaryo 2: PHP memory_limit ve a\u011f\u0131r rapor i\u015fleri<\/span><\/h3>\n<p><code>memory_limit<\/code>, PHP\u2019nin script i\u00e7in izledi\u011fi bellek tahsislerini s\u0131n\u0131rlar; t\u00fcm s\u00fcre\u00e7 RSS\u2019sini, payla\u015f\u0131lan belle\u011fi veya alt s\u00fcre\u00e7leri tek bir toplam tavanla s\u0131n\u0131rlamaz. 256M\/512M gibi de\u011ferleri tek ba\u015f\u0131na \u201cy\u00fcksek\u201d saymak yerine ger\u00e7ek istek ihtiyac\u0131 ve e\u015fzamanl\u0131 PHP s\u00fcre\u00e7leriyle birlikte b\u00fct\u00e7eleyin. Limit kaynak ay\u0131rmaz; a\u015f\u0131lmas\u0131 PHP d\u00fczeyinde hataya yol a\u00e7abilir ve bu hata kernel OOM kill ile ayn\u0131 olay de\u011fildir.<\/p>\n<p>Bu dengeyi kurmak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/php-bellek-sure-dosya-yukleme-limitleri\/\">PHP memory_limit ve di\u011fer kritik ayarlar\u0131 do\u011fru yapmak<\/a> \u00fczerine haz\u0131rlad\u0131\u011f\u0131m\u0131z rehbere g\u00f6z atman\u0131z\u0131 \u00f6neririz. Do\u011fru limitler, e\u015fzamanl\u0131 s\u00fcre\u00e7 say\u0131s\u0131 ve toplam bellek b\u00fct\u00e7esiyle birlikte belirlendi\u011finde OOM riskini azaltmaya yard\u0131mc\u0131 olabilir.<\/p>\n<h3><span id=\"Senaryo_3_MySQLPostgreSQL_buffer_ayarlari\">Senaryo 3: MySQL\/PostgreSQL buffer ayarlar\u0131<\/span><\/h3>\n<p><code>innodb_buffer_pool_size<\/code> veya <code>shared_buffers<\/code> de\u011ferlerini toplam veritaban\u0131 belle\u011fi sanmay\u0131n. Ba\u011flant\u0131lar, sorgu i\u015flemleri, bak\u0131m i\u015fleri ve di\u011fer tamponlar ek bellek kullan\u0131r. PostgreSQL\u2019de <code>work_mem<\/code> tek sunucu toplam\u0131 de\u011fil, sorgu i\u00e7indeki i\u015flemler i\u00e7in taban s\u0131n\u0131rd\u0131r; birden fazla i\u015flem ve oturumla \u00e7arp\u0131labilir. Ayn\u0131 VPS\u2019te PHP-FPM, Nginx, Redis ve yedekleme i\u015fleri varsa t\u00fcm bile\u015fenleri tek ortak b\u00fct\u00e7ede de\u011ferlendirin.<\/p>\n<p>\u00d6zellikle b\u00fcy\u00fck kataloglu e-ticaret projelerinde bu ayarlar\u0131n sorgu optimizasyonu ile birlikte d\u00fc\u015f\u00fcn\u00fclmesi gerekir. Bunun i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/woocommerce-ve-buyuk-katalog-siteleri-icin-mysql-indeksleme-ve-sorgu\/\">WooCommerce ve b\u00fcy\u00fck katalog siteleri i\u00e7in MySQL optimizasyon rehberi<\/a>nde indeks ve sorgu d\u00fczenlemelerinin kaynak kullan\u0131m\u0131na etkisini ele al\u0131yoruz; ger\u00e7ek kazan\u0131m\u0131 i\u015f y\u00fck\u00fcn\u00fczde \u00f6l\u00e7\u00fcn.<\/p>\n<h3><span id=\"Senaryo_4_Izleme_log_ve_backup_surecleri\">Senaryo 4: \u0130zleme, log ve backup s\u00fcre\u00e7leri<\/span><\/h3>\n<p>Ana uygulaman\u0131n yan\u0131nda izleme ajanlar\u0131, log toplay\u0131c\u0131lar\u0131, yedekleme ve s\u0131k\u0131\u015ft\u0131rma i\u015fleri de bellek t\u00fcketir. S\u0131k\u0131\u015ft\u0131rma seviyesi, paralellik ve i\u015flenen veri boyutuna g\u00f6re ge\u00e7ici art\u0131\u015flar olu\u015fabilir; yaln\u0131zca disk I\/O\u2019nun y\u00fcksek olmas\u0131 y\u00fcksek RAM t\u00fcketimini kan\u0131tlamaz. Bu i\u015fleri e\u015fzamanl\u0131 kapasite hesab\u0131na dahil edin.<\/p>\n<p>Bu y\u00fczden VPS \u00fczerinde t\u00fcm s\u00fcre\u00e7leri u\u00e7tan uca izlemek kritik. <a href=\"https:\/\/www.dchost.com\/blog\/vps-kaynak-izleme\/\">htop, iotop, Netdata ve Prometheus ile VPS kaynak kullan\u0131m\u0131 izleme rehberimizde<\/a> RAM, CPU ve disk IO\u2019yu birlikte izleyerek dar bo\u011fazlar\u0131 nas\u0131l tespit edebilece\u011finizi g\u00f6steriyoruz.<\/p>\n<h2><span id=\"Adim_Adim_RAM_ve_Swap_Teshisi\">Ad\u0131m Ad\u0131m RAM ve Swap Te\u015fhisi<\/span><\/h2>\n<h3><span id=\"free_tophtop_ve_proc_uzerinden_temel_analiz\">free, top\/htop ve \/proc \u00fczerinden temel analiz<\/span><\/h3>\n<p>Bellek sorunu ya\u015fad\u0131\u011f\u0131n\u0131zda ilk bakman\u0131z gerekenler:<\/p>\n<ul>\n<li><code>free -h<\/code>: Toplam, kullan\u0131lan, bo\u015f, buff\/cache ve available g\u00f6r\u00fcn\u00fcm\u00fc; s\u00fcr\u00fcm\u00fcn hesap tan\u0131m\u0131na g\u00f6re yorumlay\u0131n.<\/li>\n<li><code>top<\/code> veya <code>htop<\/code>: S\u00fcre\u00e7lerin yerle\u015fik bellek kullan\u0131m\u0131n\u0131 inceleyin; RSS toplam\u0131 payla\u015f\u0131lan sayfalar\u0131 tekrar sayabilir.<\/li>\n<li><code>vmstat 1<\/code>: \u0130lk rapordaki oranlar a\u00e7\u0131l\u0131\u015ftan bu yana ortalamad\u0131r; sonraki raporlar bir saniyelik aral\u0131\u011f\u0131 g\u00f6sterir. S\u00fcre\u00e7 ve bellek alanlar\u0131 her iki durumda anl\u0131kt\u0131r. Desteklenen s\u00fcr\u00fcmde <code>vmstat -y 1<\/code> ilk raporu atlar.<\/li>\n<\/ul>\n<p>\u00d6rnek bir te\u015fhis ak\u0131\u015f\u0131:<\/p>\n<ol>\n<li><code>free -h<\/code> ile <em>available<\/em> ve <em>Swap used<\/em> de\u011ferlerine bak\u0131n; ayn\u0131 anda servis\/cgroup s\u0131n\u0131rlar\u0131n\u0131 kontrol edin.<\/li>\n<li><code>htop<\/code>\u2019ta <code>RES<\/code> s\u00fctununa g\u00f6re s\u0131ralay\u0131n. Payla\u015f\u0131lan bellek i\u00e7in uygun yetkiyle <code>\/proc\/PID\/smaps_rollup<\/code> i\u00e7indeki PSS veya grubun toplam\u0131n\u0131 de\u011ferlendirin.<\/li>\n<li>OOM \u015f\u00fcphesi varsa <code>dmesg | grep -i oom<\/code> e\u015fle\u015fmelerini \u00e7evreleyen kay\u0131tlarla birlikte inceleyin; gerekiyorsa systemd-oomd ve uygulama g\u00fcnl\u00fcklerini de kontrol edin.<\/li>\n<\/ol>\n<h3><span id=\"Swap_kullanimini_dogru_okumak\">Swap kullan\u0131m\u0131n\u0131 do\u011fru okumak<\/span><\/h3>\n<p><code>Swap used=0<\/code>, tek ba\u015f\u0131na sorun de\u011fildir; swap tan\u0131mlanmam\u0131\u015f veya kullan\u0131lmam\u0131\u015f olabilir. Dolu swap de tek ba\u015f\u0131na aktif bellek bask\u0131s\u0131n\u0131 kan\u0131tlamaz: uzun s\u00fcredir eri\u015filmeyen sayfalar swap\u2019te kalabilir. Kullan\u0131m e\u011filimini <code>available<\/code>, servis s\u0131n\u0131rlar\u0131, swap giri\u015f\/\u00e7\u0131k\u0131\u015f oranlar\u0131 ve uygulama gecikmesiyle birlikte de\u011ferlendirin.<\/p>\n<p>Yaln\u0131zca doluluk grafi\u011fini temizlemek i\u00e7in <code>swapoff<\/code> \u00e7al\u0131\u015ft\u0131rmay\u0131n; swap\u2019teki sayfalar\u0131n geri al\u0131nmas\u0131 bellek ister ve yeterli kapasite yoksa i\u015flem ba\u015far\u0131s\u0131z olabilir. Swap de\u011fi\u015fikliklerini i\u015f y\u00fck\u00fc ve kurtarma plan\u0131yla test edin.<\/p>\n<p>\u0130nceleme i\u00e7in \u015fu g\u00f6stergeleri birlikte kaydedin:<\/p>\n<ul>\n<li>Swap toplam\u0131, kullan\u0131lan miktar ve i\u015f y\u00fck\u00fcn\u00fcn swap kullanmas\u0131na ili\u015fkin sa\u011flay\u0131c\u0131\/cgroup izinleri<\/li>\n<li>Y\u00fck alt\u0131nda <code>available<\/code>, uygulama gecikmesi ve varsa PSI bellek bekleme \u00f6l\u00e7\u00fcmleri<\/li>\n<li><code>vmstat<\/code> sonraki aral\u0131k raporlar\u0131nda <code>si\/so<\/code>: saniyelik swap giri\u015f\/\u00e7\u0131k\u0131\u015f\u0131; <code>-S<\/code> birim se\u00e7imine dikkat edin. Bunlar genel disk <code>bi\/bo<\/code> alanlar\u0131 de\u011fildir.<\/li>\n<\/ul>\n<h3><span id=\"Detayli_izleme_ve_alarmlar\">Detayl\u0131 izleme ve alarmlar<\/span><\/h3>\n<p>Ge\u00e7ici anl\u0131k kontrollerin yan\u0131nda zaman serisi izleme, farkl\u0131 servislerin bellek art\u0131\u015flar\u0131n\u0131 ili\u015fkilendirmeye yard\u0131mc\u0131 olur. \u0130\u015fletim sistemi metrikleri i\u00e7in uygun exporter, s\u00fcre\u00e7\/cgroup \u00f6l\u00e7\u00fcmleri i\u00e7in bunlar\u0131 sa\u011flayan ayr\u0131 toplama d\u00fczeni gerekir. Prometheus veriyi toplar, Grafana sorgulay\u0131p g\u00f6rselle\u015ftirir; bu ara\u00e7lar\u0131n kurulmas\u0131 tek ba\u015f\u0131na b\u00fct\u00fcn OOM olaylar\u0131n\u0131 veya s\u00fcre\u00e7leri izlemez.<\/p>\n<p>Bu konuda ba\u015flang\u0131\u00e7 yapmak isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/vps-izleme-prometheus-grafana-uptime-kuma\/\">VPS izleme ve alarm kurulumu rehberimizde<\/a> RAM ve CPU gibi temel metrikler i\u00e7in pratik alarm \u00f6rnekleri payla\u015ft\u0131k.<\/p>\n<h2><span id=\"Swap_Dosyasi_Olusturma_ve_Ayarlari\">Swap Dosyas\u0131 Olu\u015fturma ve Ayarlar\u0131<\/span><\/h2>\n<h3><span id=\"Swap_boyutunu_nasil_secmeli\">Swap boyutunu nas\u0131l se\u00e7meli?<\/span><\/h3>\n<p>Swap boyutu i\u00e7in sabit bir RAM \u00e7arpan\u0131 veya asgari de\u011fer yoktur. A\u015fa\u011f\u0131daki aral\u0131klar zorunlu \u00f6neri de\u011fil, test edilecek <strong>varsay\u0131msal ba\u015flang\u0131\u00e7 \u00f6rnekleridir<\/strong>; aktif \u00e7al\u0131\u015fma k\u00fcmesi, disk bo\u015flu\u011fu, kabul edilen gecikme ve kurtarma davran\u0131\u015f\u0131 sonucu belirler:<\/p>\n<ul>\n<li>2 GiB veya daha az RAM: \u00f6rnek olarak 1\u20132 GiB swap<\/li>\n<li>2 GiB \u00fczeri, 8 GiB dahil RAM: \u00f6rnek olarak 2\u20134 GiB swap<\/li>\n<li>8 GiB \u00fczeri RAM: \u00f6rnek olarak 4\u20138 GiB swap; daha az, daha fazla veya swapsiz tasar\u0131m i\u015f y\u00fck\u00fcne g\u00f6re de\u011ferlendirilebilir.<\/li>\n<\/ul>\n<p>Dosyan\u0131n b\u00fcy\u00fck olmas\u0131 tek ba\u015f\u0131na swap I\/O \u00fcretmez; \u00f6nemli olan hangi sayfalar\u0131n ne s\u0131kl\u0131kla ta\u015f\u0131nd\u0131\u011f\u0131d\u0131r. Diskte i\u015fletim ve yedekleme i\u00e7in yeterli bo\u015fluk b\u0131rak\u0131n. S\u00fcrekli swap trafi\u011fiyle birlikte gecikme art\u0131yorsa yaln\u0131zca dosyay\u0131 b\u00fcy\u00fctmek yerine \u00e7al\u0131\u015fma k\u00fcmesini, e\u015fzamanl\u0131l\u0131\u011f\u0131 ve RAM kapasitesini inceleyin. NVMe etiketi \u00f6l\u00e7\u00fclm\u00fc\u015f gecikme veya istikrar garantisi de\u011fildir.<\/p>\n<h3><span id=\"Swap_dosyasi_olusturma_ornegi\">Swap dosyas\u0131 olu\u015fturma \u00f6rne\u011fi<\/span><\/h3>\n<p>A\u015fa\u011f\u0131daki \u00f6rnek <strong>yerel, normal bir ext4\/XFS dosya sisteminde yeni bir 2 GiB dosya<\/strong> i\u00e7indir. Root kabu\u011fu, yeterli bo\u015f alan ve ortam\u0131n swap etkinle\u015ftirmeye izin vermesi gerekir. <code>\/swapfile<\/code> mevcutsa veya sembolik ba\u011flant\u0131ysa durun; mevcut dosyay\u0131 yeniden bi\u00e7imlendirmeyin. Her sat\u0131r\u0131 ayr\u0131 \u00e7al\u0131\u015ft\u0131r\u0131n ve hata oldu\u011funda sonraki ad\u0131ma ge\u00e7meyin. <code>conv=excl<\/code> mevcut hedefin \u00fczerine yaz\u0131lmas\u0131n\u0131 reddeder:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">umask 077\ndd if=\/dev\/zero of=\/swapfile bs=1M count=2048 status=progress conv=excl\nchmod 600 \/swapfile\nmkswap \/swapfile\nswapon \/swapfile\n<\/code><\/pre>\n<p>\u00d6n ay\u0131rman\u0131n desteklendi\u011fi do\u011frulanm\u0131\u015f dosya sisteminde olu\u015fturma sat\u0131r\u0131 yerine <code>fallocate -l 2G \/swapfile<\/code> kullan\u0131labilir; iki olu\u015fturma y\u00f6ntemini birlikte uygulamay\u0131n. XFS \u00f6n ayr\u0131lm\u0131\u015f swap dosyalar\u0131n\u0131 Linux 4.18\u2019den beri destekler. <code>truncate<\/code> veya seyrek kopyalarla delikli dosya olu\u015fturmay\u0131n. Btrfs\/COW, s\u0131k\u0131\u015ft\u0131rma, snapshot veya a\u011f dosya sistemi i\u00e7in bu genel tarifi kullanmay\u0131n: Btrfs\u2019te NODATACOW, deliksiz yerle\u015fim ve ayg\u0131t\/profil k\u0131s\u0131tlar\u0131 vard\u0131r; <a href=\"https:\/\/btrfs.readthedocs.io\/en\/latest\/Swapfile.html\" rel=\"nofollow noopener\" target=\"_blank\">Btrfs swapfile belgesindeki<\/a> s\u00fcr\u00fcme uygun y\u00f6ntemi ayr\u0131ca izleyin.<\/p>\n<p>Yaln\u0131zca <code>swapon<\/code> ba\u015far\u0131yla bittikten ve <code>swapon --show<\/code> yeni dosyay\u0131 listeledikten sonra, mevcut <code>\/etc\/fstab<\/code> dosyas\u0131n\u0131n yede\u011fini al\u0131p ayn\u0131 yol i\u00e7in kay\u0131t yoksa \u015fu sat\u0131r\u0131 ekleyin. Systemd kullanan sistemde de\u011fi\u015fiklikten sonra <code>systemctl daemon-reload<\/code> \u00e7al\u0131\u015ft\u0131r\u0131n. Dosyay\u0131 bar\u0131nd\u0131ran b\u00f6l\u00fcm\u00fcn a\u00e7\u0131l\u0131\u015fta haz\u0131r olmas\u0131n\u0131 ve yeniden ba\u015flatma sonras\u0131 etkinle\u015fmeyi planl\u0131 bak\u0131mda do\u011frulay\u0131n:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">\/swapfile   none    swap    sw    0   0\n<\/code><\/pre>\n<p>Mevcut swap durumunu g\u00f6rmek i\u00e7in:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">swapon --show\nfree -h\n<\/code><\/pre>\n<h3><span id=\"vmswappiness_ve_diger_kernel_ayarlari\">vm.swappiness ve di\u011fer kernel ayarlar\u0131<\/span><\/h3>\n<p>Linux 6.12\u2019de <code>vm.swappiness<\/code> aral\u0131\u011f\u0131 <strong>0\u2013200<\/strong>, \u00e7ekirdek varsay\u0131lan\u0131 60\u2019t\u0131r; da\u011f\u0131t\u0131m farkl\u0131 de\u011fer ayarlayabilir. De\u011fer, swap I\/O ile dosya sayfalamas\u0131n\u0131n g\u00f6reli maliyetini ifade eder; kullan\u0131lan RAM y\u00fczdesi veya \u201cbu seviyede swap ba\u015flat\u201d e\u015fi\u011fi de\u011fildir. 100, e\u015fit maliyet varsay\u0131m\u0131d\u0131r; daha d\u00fc\u015f\u00fck de\u011fer swap\u2019\u0131 g\u00f6rece pahal\u0131 sayar. 0 swap\u2019\u0131 kapatmaz: \u00e7ekirdek bir b\u00f6lgedeki bo\u015f ve dosya destekli sayfalar y\u00fcksek su e\u015fi\u011finin alt\u0131na inene kadar swap ba\u015flatmaz. 100 \u00fczeri de\u011ferler zram veya g\u00f6rece h\u0131zl\u0131 swap d\u00fczenlerinde anlaml\u0131 olabilir. A\u015fa\u011f\u0131daki 20 yaln\u0131zca \u00f6l\u00e7\u00fclerek denenecek \u00f6rnektir.<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sysctl vm.swappiness\nsysctl -w vm.swappiness=20\n<\/code><\/pre>\n<p>\u00d6nce mevcut de\u011feri kaydedin; \u00f6l\u00e7\u00fcm k\u00f6t\u00fcle\u015firse <code>sysctl -w vm.swappiness=ESKI_DEGER<\/code> i\u00e7indeki yer tutucuyu o say\u0131yla de\u011fi\u015ftirerek geri d\u00f6n\u00fcn. Uygun buldu\u011funuz de\u011feri kal\u0131c\u0131 yapmak i\u00e7in \u00f6rne\u011fin <code>\/etc\/sysctl.d\/90-vps-memory.conf<\/code> kullanabilirsiniz; ayn\u0131 anahtar\u0131n di\u011fer dosyalardaki tan\u0131mlar\u0131n\u0131 ve y\u00fckleme s\u0131ras\u0131n\u0131 kontrol edin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">vm.swappiness = 20\nvm.vfs_cache_pressure = 100\n<\/code><\/pre>\n<p><code>vm.vfs_cache_pressure<\/code>, inode\/dentry \u00f6nbelleklerinin geri kazan\u0131m e\u011filimini y\u00f6netir. Linux 6.12\u2019de 100 varsay\u0131land\u0131r; \u00f6rnekte bu de\u011fer korunuyor, ayr\u0131ca de\u011fi\u015ftirmek zorunda de\u011filsiniz. 0 bu \u00f6nbelleklerin bellek bask\u0131s\u0131yla geri al\u0131nmas\u0131n\u0131 engelleyerek OOM riskini art\u0131rabilir; \u00e7ok y\u00fcksek de\u011ferler de maliyetlidir. Kaydetmek \u00e7al\u0131\u015fan de\u011feri kendili\u011finden de\u011fi\u015ftirmez: test edilen anahtar\u0131 hedefli olarak uygulay\u0131p <code>sysctl<\/code> ile do\u011frulay\u0131n ve a\u00e7\u0131l\u0131\u015fta y\u00fcklenen de\u011feri bak\u0131m sonras\u0131nda kontrol edin.<\/p>\n<h2><span id=\"OOM_Killeri_Yonetmek_Onleme_Sinirlama_ve_Izleme\">OOM Killer\u2019\u0131 Y\u00f6netmek: \u00d6nleme, S\u0131n\u0131rlama ve \u0130zleme<\/span><\/h2>\n<h3><span id=\"Overcommit_ayarlari\">Overcommit ayarlar\u0131<\/span><\/h3>\n<p>Overcommit, belirli sanal bellek e\u015flemeleri i\u00e7in taahh\u00fct edilen belle\u011fin hesaplanma ve kabul edilme politikas\u0131d\u0131r; bir s\u00fcrecin sanal adres alan\u0131n\u0131 RAM + swap toplam\u0131yla e\u015fitlemez. A\u015fa\u011f\u0131daki anahtarlarla politikay\u0131 inceleyebilirsiniz; ayr\u0131ca <code>\/proc\/meminfo<\/code> i\u00e7indeki <code>CommitLimit<\/code> ve <code>Committed_AS<\/code> alanlar\u0131na bak\u0131n:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">sysctl vm.overcommit_memory\nsysctl vm.overcommit_ratio\n<\/code><\/pre>\n<p>De\u011ferler k\u0131saca:<\/p>\n<ul>\n<li><strong>vm.overcommit_memory=0:<\/strong> Varsay\u0131lan sezgisel politika; a\u00e7\u0131k\u00e7a a\u015f\u0131r\u0131 taahh\u00fctleri reddedebilir.<\/li>\n<li><strong>1:<\/strong> Taahh\u00fct hesab\u0131 a\u00e7\u0131s\u0131ndan a\u015f\u0131r\u0131 tahsise izin verir; ger\u00e7ek sayfa tahsisinin veya sonraki eri\u015fimin ba\u015far\u0131l\u0131 olaca\u011f\u0131n\u0131 garanti etmez.<\/li>\n<li><strong>2:<\/strong> Taahh\u00fct s\u0131n\u0131r\u0131n\u0131 swap + yap\u0131land\u0131r\u0131lan fiziksel RAM pay\u0131yla s\u0131n\u0131rlar. Bu pay <code>vm.overcommit_ratio<\/code> veya <code>vm.overcommit_kbytes<\/code> ile belirlenir; bu iki ayar mode 2\u2019de anlaml\u0131d\u0131r.<\/li>\n<\/ul>\n<p>Mode 2, uygulaman\u0131n bellek tahsisi hatalar\u0131n\u0131 daha erken g\u00f6rmesine yol a\u00e7abilir; her veritaban\u0131 veya karma i\u015f y\u00fck\u00fc i\u00e7in otomatik olarak daha iyi de\u011fildir. Mevcut politika, taahh\u00fct s\u0131n\u0131r\u0131, uygulaman\u0131n hata davran\u0131\u015f\u0131 ve cgroup s\u0131n\u0131rlar\u0131n\u0131 birlikte test edin. Overcommit ayar\u0131n\u0131 de\u011fi\u015ftirmek RAM kapasitesinin veya servis b\u00fct\u00e7esinin yerine ge\u00e7mez.<\/p>\n<h3><span id=\"systemd_ile_servis_bazli_bellek_limitleri\">systemd ile servis bazl\u0131 bellek limitleri<\/span><\/h3>\n<p>A\u015fa\u011f\u0131daki \u00f6rnek systemd 243+ ve etkin bellek denetleyicisine sahip <strong>cgroup v2<\/strong> d\u00fczenini hedefler. Servis ad\u0131 da\u011f\u0131t\u0131ma g\u00f6re <code>php-fpm.service<\/code> veya <code>php8.x-fpm.service<\/code> olabilir; kurulu ger\u00e7ek birimi do\u011frulay\u0131n. \u00d6rnekteki <code>php-fpm.service<\/code> ad\u0131n\u0131 b\u00fct\u00fcn ad\u0131mlarda ayn\u0131 ger\u00e7ek adla de\u011fi\u015ftirin. 768 MiB\/1 GiB de\u011ferleri toplam b\u00fct\u00e7enize g\u00f6re do\u011frulanacak \u00f6rneklerdir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">systemctl edit php-fpm.service\n<\/code><\/pre>\n<p>A\u00e7\u0131lan dosyaya:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">[Service]\nMemoryHigh=768M\nMemoryMax=1G\n<\/code><\/pre>\n<p>Yaln\u0131zca ilgili override dosyas\u0131n\u0131 kaydedin; mevcut birimin di\u011fer ayarlar\u0131n\u0131 koruyun. \u00d6nce test ortam\u0131nda uygulama ve i\u015f y\u00fck\u00fc davran\u0131\u015f\u0131n\u0131 kontrol edin, sonra uygun bak\u0131m aral\u0131\u011f\u0131nda:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">systemctl daemon-reload &amp;&amp;\nsystemctl restart php-fpm.service\n<\/code><\/pre>\n<p><code>MemoryHigh<\/code> \u00fcst\u00fcnde geri kazan\u0131m bask\u0131s\u0131 ve yava\u015flatma uygulan\u0131r; tek ba\u015f\u0131na OOM kill ba\u015flatmaz. <code>MemoryMax<\/code> alt\u0131nda kullan\u0131m tutulamazsa <strong>\u00e7ekirdek ilgili cgroup i\u00e7inde OOM killer\u2019\u0131 \u00e7al\u0131\u015ft\u0131rabilir<\/strong>; baz\u0131 tahsisler hata d\u00f6nebilir ve limit k\u0131sa s\u00fcreli a\u015f\u0131labilir. Bu s\u0131n\u0131r toplam s\u00fcre\u00e7\/cgroup bellek hesab\u0131yla ilgilidir; swap i\u00e7in <code>MemorySwapMax<\/code> ayr\u0131d\u0131r. \u00dcst cgroup s\u0131n\u0131rlar\u0131 da sonucu etkiler.<\/p>\n<p>Bu \u00f6rnek yeniden ba\u015flatma politikas\u0131 eklemez. <code>OOMPolicy<\/code> OOM sonras\u0131 servis grubunun davran\u0131\u015f\u0131n\u0131, <code>Restart<\/code> ise ba\u015far\u0131s\u0131zl\u0131k sonras\u0131 yeniden ba\u015flatma ko\u015fulunu belirler. Etkin de\u011ferleri <code>systemctl show php-fpm.service -p MemoryHigh -p MemoryMax -p MemorySwapMax -p OOMPolicy -p Restart<\/code> ile inceleyin; sistemde desteklenen <code>memory.events<\/code> saya\u00e7lar\u0131n\u0131 da izleyin. Geri d\u00f6n\u00fc\u015fte yaln\u0131zca ekledi\u011finiz ayarlar\u0131 kald\u0131r\u0131p eski de\u011ferleri y\u00fckleyin; di\u011fer override dosyalar\u0131n\u0131 silmeyin.<\/p>\n<h3><span id=\"OOM_scorer_ile_kritik_surecleri_korumak\">OOM scorer ile kritik s\u00fcre\u00e7leri korumak<\/span><\/h3>\n<p>Kritik bir servisin uygun kernel OOM adaylar\u0131 aras\u0131ndaki se\u00e7ilme e\u011filimini azaltmak i\u00e7in unit override i\u00e7inde \u00f6rne\u011fin \u015fu ayar de\u011ferlendirilebilir. Bu bir bellek s\u0131n\u0131r\u0131 veya kaynak rezervasyonu de\u011fildir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">[Service]\nOOMScoreAdjust=-500\n<\/code><\/pre>\n<p><code>OOMScoreAdjust<\/code> \u22121000 ile +1000 aras\u0131ndad\u0131r. \u2212500 se\u00e7ilme e\u011filimini azalt\u0131r, pozitif de\u011fer art\u0131r\u0131r; \u22121000 ola\u011fan kernel OOM adayl\u0131\u011f\u0131ndan d\u0131\u015flar. Bunu b\u00fct\u00fcn servislere uygulamak se\u00e7ilebilir kurban b\u0131rakmayabilir ve sorunu a\u011f\u0131rla\u015ft\u0131rabilir. Ayar ba\u015fka bir s\u00fcre\u00e7 y\u00f6neticisinin veya y\u00f6neticinin a\u00e7\u0131k\u00e7a g\u00f6nderdi\u011fi sinyalin s\u00fcreci durdurmas\u0131n\u0131 engellemez. Mevcut de\u011feri kaydedin; test ortam\u0131nda servislerin birlikte davran\u0131\u015f\u0131n\u0131 inceleyip yaln\u0131zca gerekli override sat\u0131r\u0131n\u0131 geri al\u0131n.<\/p>\n<h2><span id=\"Uygulama_Tarafi_PHP_Nodejs_Java_ve_Digerleri\">Uygulama Taraf\u0131: PHP, Node.js, Java ve Di\u011ferleri<\/span><\/h2>\n<h3><span id=\"PHP_ve_PHP-FPM_icin_pratik_oneriler\">PHP ve PHP-FPM i\u00e7in pratik \u00f6neriler<\/span><\/h3>\n<p>PHP i\u015f y\u00fck\u00fcnde script ba\u015f\u0131na t\u00fcketim ile e\u015fzamanl\u0131 s\u00fcre\u00e7 say\u0131s\u0131n\u0131 birlikte s\u0131n\u0131rlay\u0131n. A\u015fa\u011f\u0131daki ayarlar farkl\u0131 ama\u00e7lara hizmet eder:<\/p>\n<ul>\n<li><strong>memory_limit:<\/strong> PHP\u2019nin script bellek hesab\u0131 i\u00e7in ger\u00e7ek ihtiyaca g\u00f6re se\u00e7in; b\u00fct\u00fcn servis RSS\u2019sinin s\u0131n\u0131r\u0131 saymay\u0131n.<\/li>\n<li><strong>pm.max_children:<\/strong> \u0130\u015fletim sistemi, veritaban\u0131, cache ve di\u011fer i\u015fler ayr\u0131ld\u0131ktan sonra PHP\u2019ye kalan b\u00fct\u00e7eyi kullan\u0131n. Temsil\u00ee yo\u011fun y\u00fckte s\u00fcre\u00e7 t\u00fcketimini \u00f6l\u00e7\u00fcn, tepe pay\u0131 b\u0131rak\u0131n ve RSS\u2019de payla\u015f\u0131lan sayfalar\u0131 tekrar saymamaya dikkat edin.<\/li>\n<li><strong>pm.max_requests:<\/strong> Belirli istek say\u0131s\u0131ndan sonra child s\u00fcreci yeniler; birikimi s\u0131n\u0131rlayabilir, bellek ka\u00e7a\u011f\u0131n\u0131n nedenini d\u00fczeltmez.<\/li>\n<\/ul>\n<p>Bu parametreleri ger\u00e7ek senaryolar \u00fczerinden nas\u0131l hesaplayaca\u011f\u0131n\u0131z\u0131 zaten <a href=\"https:\/\/www.dchost.com\/blog\/wordpress-ve-woocommerce-icin-php-fpm-ayarlari-pm-max-children\/\">PHP-FPM ayarlar\u0131 rehberimizde<\/a> ad\u0131m ad\u0131m g\u00f6sterdik. Bu rehberi RAM ve OOM y\u00f6netimiyle birlikte d\u00fc\u015f\u00fcnmek en sa\u011fl\u0131kl\u0131 yakla\u015f\u0131m olacakt\u0131r.<\/p>\n<h3><span id=\"Nodejs_uygulamalari\">Node.js uygulamalar\u0131<\/span><\/h3>\n<p>Node.js\u2019in JavaScript olay d\u00f6ng\u00fcs\u00fc ile b\u00fct\u00fcn s\u00fcre\u00e7\/i\u015f par\u00e7ac\u0131\u011f\u0131 modeli ayn\u0131 \u015fey de\u011fildir; worker threads, yerel k\u00fct\u00fcphaneler ve Buffer nesneleri de bellek kullanabilir. Yo\u011fun JSON i\u015fleme, b\u00fcy\u00fck sorgu sonu\u00e7lar\u0131 ve s\u0131n\u0131rs\u0131z cache i\u00e7in toplam s\u00fcre\u00e7 belle\u011fini \u00f6l\u00e7\u00fcn:<\/p>\n<ul>\n<li>PM2 veya systemd ile s\u00fcre\u00e7 ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc y\u00f6netirken <code>--max-old-space-size<\/code> se\u00e7ene\u011finin MiB cinsinden yaln\u0131zca V8 old-space alan\u0131n\u0131 s\u0131n\u0131rlad\u0131\u011f\u0131n\u0131 bilin; toplam RSS tavan\u0131 de\u011fildir.<\/li>\n<li>Her instance\u2019\u0131n gen\u00e7 nesil heap, Buffer\/yerel bellek ve di\u011fer ek y\u00fckleri dahil t\u00fcketimini b\u00fct\u00e7eleyin; gerekiyorsa ayr\u0131 cgroup toplam s\u0131n\u0131r\u0131 kullan\u0131n.<\/li>\n<li>Uzun ya\u015fayan in-memory cache ve i\u015f kuyruklar\u0131n\u0131n boyutlar\u0131n\u0131 s\u0131n\u0131rlay\u0131n; otomatik yeniden ba\u015flatmay\u0131 ka\u00e7a\u011f\u0131n \u00e7\u00f6z\u00fcm\u00fc saymay\u0131n.<\/li>\n<\/ul>\n<p>Node.js projelerini canl\u0131ya al\u0131rken genel mimariyi nas\u0131l kuraca\u011f\u0131n\u0131z\u0131 merak ediyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/node-js-uygulamalarini-nerede-host-etmeli-cpanel-paylasimli-hosting\/\">Node.js uygulamalar\u0131n\u0131 host etme rehberimizde<\/a> VPS taraf\u0131ndaki temel yakla\u015f\u0131mlar\u0131 \u00f6zetledik.<\/p>\n<h3><span id=\"Java_ve_JVM_tabanli_uygulamalar\">Java ve JVM tabanl\u0131 uygulamalar<\/span><\/h3>\n<p>Java\/Kotlin servislerinde <code>-Xms<\/code> ba\u015flang\u0131\u00e7\/minimum Java heap\u2019ini, <code>-Xmx<\/code> maksimum heap\u2019i belirler; bunlar JVM s\u00fcrecinin toplam bellek s\u0131n\u0131r\u0131 de\u011fildir. B\u00fct\u00e7ede \u015funlar\u0131 ay\u0131r\u0131n:<\/p>\n<ul>\n<li>\u0130\u015fletim sistemi ve di\u011fer servislerin bellek ihtiyac\u0131<\/li>\n<li>Heap yan\u0131nda Metaspace, i\u015f par\u00e7ac\u0131\u011f\u0131 y\u0131\u011f\u0131nlar\u0131, do\u011frudan\/yerel tamponlar ve GC ek y\u00fck\u00fc<\/li>\n<li>Container\/cgroup s\u0131n\u0131rlar\u0131 ve kullan\u0131lan JDK\u2019nin bu ortam\u0131 alg\u0131lama davran\u0131\u015f\u0131<\/li>\n<\/ul>\n<p>JVM varsay\u0131lanlar\u0131 s\u00fcr\u00fcme ve ortama g\u00f6re se\u00e7ilir; evrensel olarak fazla b\u00fcy\u00fck saymay\u0131n. Heap OOM hatas\u0131 ile kernel\u2019in JVM s\u00fcrecini \u00f6ld\u00fcrmesini g\u00fcnl\u00fcklerden ay\u0131r\u0131n; y\u00fck testiyle heap, toplam s\u00fcre\u00e7 t\u00fcketimi ve cgroup hareket alan\u0131n\u0131 birlikte do\u011frulay\u0131n.<\/p>\n<h2><span id=\"Kapasite_Planlama_ve_Onleyici_Stratejiler\">Kapasite Planlama ve \u00d6nleyici Stratejiler<\/span><\/h2>\n<h3><span id=\"Baslangicta_dogru_VPS_boyutlandirmasi\">Ba\u015flang\u0131\u00e7ta do\u011fru VPS boyutland\u0131rmas\u0131<\/span><\/h3>\n<p>Kapasite plan\u0131nda yaln\u0131zca ziyaret\u00e7i say\u0131s\u0131n\u0131 de\u011fil e\u015fzamanl\u0131 i\u015f say\u0131s\u0131n\u0131, temsil\u00ee tepe belle\u011fini, arka plan g\u00f6revlerini ve servis s\u0131n\u0131rlar\u0131n\u0131 birlikte de\u011ferlendirin. Uygun RAM kapasitesi hareket alan\u0131 sa\u011flar; hatal\u0131 bir cgroup limiti veya s\u00fcrekli b\u00fcy\u00fcyen bellek ka\u00e7a\u011f\u0131 yaln\u0131zca daha b\u00fcy\u00fck VPS ile \u00e7\u00f6z\u00fclmeyebilir.<\/p>\n<p>Yeni bir proje i\u00e7in temel hesaplara nereden ba\u015flayaca\u011f\u0131n\u0131z\u0131 bilmiyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/yeni-web-sitesi-icin-cpu-ram-ve-trafik-nasil-hesaplanir\/\">yeni web sitesi i\u00e7in CPU, RAM ve trafik hesaplama rehberimizde<\/a> kapasite planlamas\u0131 i\u00e7in kullan\u0131labilir pratik form\u00fcller payla\u015ft\u0131k. Hesaplar\u0131 temsil\u00ee y\u00fck alt\u0131nda do\u011frulay\u0131p \u00f6l\u00e7\u00fclen tepelere uygun pay b\u0131rak\u0131n; tek bir tahmin OOM ya\u015fanmayaca\u011f\u0131n\u0131 g\u00f6stermez.<\/p>\n<h3><span id=\"Periyodik_izleme_ve_trend_analizi\">Periyodik izleme ve trend analizi<\/span><\/h3>\n<p>Bellek sorunlar\u0131 yava\u015f b\u00fcy\u00fcyen bir e\u011filimle veya k\u0131sa bir ani taleple ortaya \u00e7\u0131kabilir. Her iki durumu yakalamak i\u00e7in d\u00fczenli \u00f6l\u00e7\u00fcm al\u0131n:<\/p>\n<ul>\n<li>RAM ve swap kullan\u0131m\u0131n\u0131 g\u00fcnl\u00fck\/haftal\u0131k grafiklerle izleyin.<\/li>\n<li>Yeni s\u00fcr\u00fcm da\u011f\u0131t\u0131mlar\u0131ndan sonra bellek trendini yak\u0131ndan takip edin.<\/li>\n<li>Veritaban\u0131 veya cache yap\u0131land\u0131rmas\u0131 de\u011fi\u015fikliklerinden sonra metrikleri kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/li>\n<\/ul>\n<p>Bu \u00f6l\u00e7\u00fcmleri zaman i\u00e7inde kar\u015f\u0131la\u015ft\u0131r\u0131n. Staging ortam\u0131nda temsil\u00ee y\u00fck testi yaparken RAM kullan\u0131m\u0131n\u0131, swap I\/O\u2019yu, cgroup olaylar\u0131n\u0131 ve gecikmeyi birlikte kaydedin. <a href=\"https:\/\/www.dchost.com\/blog\/k6-jmeter-locust-load-test\/\">k6, JMeter ve Locust ile kapasite \u00f6l\u00e7me rehberimiz<\/a> ba\u015flang\u0131\u00e7 i\u00e7in kullan\u0131labilir; test sonucu yaln\u0131zca uygulanan senaryonun s\u0131n\u0131rlar\u0131n\u0131 g\u00f6sterir.<\/p>\n<h3><span id=\"Alarm_esigi_nasil_belirlenmeli\">Alarm e\u015fi\u011fi nas\u0131l belirlenmeli?<\/span><\/h3>\n<p>Alarm\u0131 tek bir RAM veya swap doluluk y\u00fczdesine ba\u011flamay\u0131n. Ba\u015flang\u0131\u00e7 \u00f6l\u00e7\u00fctlerini uygulaman\u0131n gecikme hedefi, \u00f6l\u00e7\u00fcm kapsam\u0131 ve m\u00fcdahale s\u00fcresiyle birlikte belirleyin:<\/p>\n<ul>\n<li><strong>RAM bask\u0131s\u0131:<\/strong> \u00d6rne\u011fin <code>MemAvailable\/MemTotal<\/code> oran\u0131n\u0131n %20\u2019nin alt\u0131nda 10 dakika kalmas\u0131 incelenecek bir ba\u015flang\u0131\u00e7 kural\u0131 olabilir; %10 gibi daha d\u00fc\u015f\u00fck e\u015fikleri uygulama etkisiyle kalibre edin. Bunlar OOM s\u0131n\u0131r\u0131 de\u011fildir.<\/li>\n<li><strong>Swap:<\/strong> Doluluk de\u011fi\u015fimini aktif <code>si\/so<\/code>, I\/O gecikmesi ve PSI ile ili\u015fkilendirin; %20\u201330 veya %50 doluluk tek ba\u015f\u0131na kritik olay tan\u0131mlamaz.<\/li>\n<li><strong>OOM ve cgroup:<\/strong> Yeni OOM kill ve artan <code>memory.events<\/code> saya\u00e7lar\u0131 i\u00e7in olay bildirimi kurun; \u00f6nem d\u00fczeyini etkilenen hizmet ve tekrar durumuna g\u00f6re belirleyin.<\/li>\n<\/ul>\n<p>PSI destekleniyorsa <code>\/proc\/pressure\/memory<\/code>, belle\u011fi bekleyerek kaybedilen zaman\u0131 g\u00f6sterir; RAM kullan\u0131m y\u00fczdesi de\u011fildir. Bildirim teslimini, eksik veriyi ve servis\/cgroup baz\u0131ndaki g\u00f6r\u00fcn\u00fcrl\u00fc\u011f\u00fc test edin. Ani talepler alarm de\u011ferlendirme aral\u0131\u011f\u0131ndan h\u0131zl\u0131 geli\u015febilir; erken uyar\u0131 garanti de\u011fildir.<\/p>\n<h2><span id=\"Sonuc_VPSte_RAM_Swap_ve_OOM_Killeri_Rayina_Oturtmak\">Sonu\u00e7: VPS\u2019te RAM, Swap ve OOM Killer\u2019\u0131 Ray\u0131na Oturtmak<\/span><\/h2>\n<p>RAM, swap, s\u00fcre\u00e7 s\u0131n\u0131rlar\u0131 ve uygulama e\u015fzamanl\u0131l\u0131\u011f\u0131 birlikte planland\u0131\u011f\u0131nda bellek davran\u0131\u015f\u0131n\u0131 a\u00e7\u0131klamak ve y\u00f6netmek kolayla\u015f\u0131r. Swap kullan\u0131p kullanmama karar\u0131 i\u015f y\u00fck\u00fcne ba\u011fl\u0131d\u0131r; OOM olay\u0131n\u0131 da yaln\u0131zca RAM doluluk grafi\u011fiyle a\u00e7\u0131klamamak gerekir. \u015eu katmanlar\u0131 birlikte de\u011ferlendirin:<\/p>\n<ul>\n<li>\u0130\u015f y\u00fck\u00fcne uygun RAM ve swap kombinasyonu<\/li>\n<li>Uygulama bazl\u0131 bellek limitleri (PHP, Node.js, Java, veritaban\u0131)<\/li>\n<li>systemd\/cgroup ve kernel (sysctl) ayarlar\u0131n\u0131n dengeli kullan\u0131m\u0131<\/li>\n<li>S\u00fcrekli izleme, alarm ve kapasite planlama<\/li>\n<\/ul>\n<p>Bu katmanlar\u0131 bir b\u00fct\u00e7e ve izleme plan\u0131nda birle\u015ftirin. VPS veya <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> se\u00e7erken kaynak s\u0131n\u0131rlar\u0131n\u0131, i\u015fletim sistemi y\u00f6netim sorumlulu\u011funu ve gerekli bellek denetleyicilerinin deste\u011fini do\u011frulay\u0131n. Servis duru\u015funda \u00f6nce kernel, cgroup, systemd-oomd ve uygulama g\u00fcnl\u00fcklerinden nedeni ay\u0131r\u0131n; ard\u0131ndan en k\u00fc\u00e7\u00fck gerekli de\u011fi\u015fikli\u011fi test edin.<\/p>\n<p>Yeni projede veya mevcut VPS\u2019i iyile\u015ftirirken mevcut de\u011ferleri kaydedin, de\u011fi\u015fiklik ba\u015f\u0131na ba\u015far\u0131 \u00f6l\u00e7\u00fct\u00fc ve geri d\u00f6n\u00fc\u015f yolu belirleyin. Temsil\u00ee y\u00fck alt\u0131nda gecikme, kullan\u0131labilir bellek, swap trafi\u011fi ve servis olaylar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n; kapasite veya mimari de\u011fi\u015fikli\u011fini bu kan\u0131tlarla se\u00e7in.<\/p>\n<h2><span id=\"Birincil_Teknik_Kaynaklar\">Birincil Teknik Kaynaklar<\/span><\/h2>\n<ul>\n<li><a href=\"https:\/\/docs.kernel.org\/6.12\/admin-guide\/sysctl\/vm.html\" rel=\"nofollow noopener\" target=\"_blank\">Linux 6.12 \u2014 VM sysctl<\/a><\/li>\n<li><a href=\"https:\/\/docs.kernel.org\/6.12\/admin-guide\/cgroup-v2.html\" rel=\"nofollow noopener\" target=\"_blank\">Linux 6.12 \u2014 cgroup v2<\/a><\/li>\n<li><a href=\"https:\/\/gitlab.com\/procps-ng\/procps\/-\/blob\/v4.0.4\/man\/free.1\" rel=\"nofollow noopener\" target=\"_blank\">procps-ng 4.0.4 \u2014 free<\/a><\/li>\n<li><a href=\"https:\/\/man7.org\/linux\/man-pages\/man8\/vmstat.8.html\" rel=\"nofollow noopener\" target=\"_blank\">procps-ng \u2014 vmstat<\/a><\/li>\n<li><a href=\"https:\/\/man7.org\/linux\/man-pages\/man8\/swapon.8.html\" rel=\"nofollow noopener\" target=\"_blank\">util-linux \u2014 swapon<\/a><\/li>\n<li><a href=\"https:\/\/www.freedesktop.org\/software\/systemd\/man\/latest\/systemd.resource-control.html\" rel=\"nofollow noopener\" target=\"_blank\">systemd \u2014 Resource Control<\/a><\/li>\n<li><a href=\"https:\/\/www.freedesktop.org\/software\/systemd\/man\/latest\/systemd.service.html\" rel=\"nofollow noopener\" target=\"_blank\">systemd \u2014 Service Configuration<\/a><\/li>\n<\/ul>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Linux VPS\u2019te kullan\u0131labilir bellek, swap trafi\u011fi ve OOM olaylar\u0131n\u0131 birlikte inceleyin. Swap dosyas\u0131, swappiness, systemd s\u0131n\u0131rlar\u0131 ve uygulama b\u00fct\u00e7eleri i\u00e7in kaynakl\u0131 rehber.<\/p>\n","protected":false},"author":1,"featured_media":12517,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-3586","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3586","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=3586"}],"version-history":[{"count":6,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3586\/revisions"}],"predecessor-version":[{"id":12519,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3586\/revisions\/12519"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/12517"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=3586"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=3586"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=3586"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}