{"id":850,"date":"2026-09-20T14:04:40","date_gmt":"2026-09-20T14:04:40","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=850"},"modified":"2026-09-20T09:40:44","modified_gmt":"2026-09-20T09:40:44","slug":"wordpress-bellek-siniri-hatasi-nasil-cozulur","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/tr\/wordpress-bellek-siniri-hatasi-nasil-cozulur\/","title":{"rendered":"WordPress Bellek S\u0131n\u0131r\u0131 Hatas\u0131 Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr?"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">H\u0131zl\u0131 \u00d6zet &#8211; WordPress Bellek S\u0131n\u0131r\u0131 Hatas\u0131<\/p>\n<p>Bu hata, bir PHP iste\u011finin kendisine ayr\u0131lan bellek limitini a\u015fmas\u0131yla olu\u015fur. \u00d6nce PHP-FPM ve WordPress katmanlar\u0131ndaki ger\u00e7ek de\u011ferleri kar\u015f\u0131la\u015ft\u0131r\u0131n, sonra kayna\u011f\u0131 t\u00fcketen eklenti veya i\u015flemi izole edin.<\/p>\n<ul>\n<li><strong>Hata anlam\u0131<\/strong> \u2014 PHP iste\u011fi, tan\u0131ml\u0131 memory_limit de\u011ferini a\u015fm\u0131\u015ft\u0131r; bu tek ba\u015f\u0131na VPS RAM&#039;inin tamamen bitti\u011fini g\u00f6stermez.<\/li>\n<li><strong>\u0130lk kontrol<\/strong> \u2014 CLI, PHP-FPM ve WordPress&#039;in bellek de\u011ferlerini ayr\u0131 ayr\u0131 \u00f6l\u00e7\u00fcn.<\/li>\n<li><strong>WordPress ayar\u0131<\/strong> \u2014 wp-config.php i\u00e7inde WP_MEMORY_LIMIT ve WP_MAX_MEMORY_LIMIT de\u011ferlerini kontroll\u00fc bi\u00e7imde d\u00fczenleyin.<\/li>\n<li><strong>PHP ayar\u0131<\/strong> \u2014 Gerekirse php.ini, .user.ini veya panel \u00fczerinden memory_limit de\u011ferini art\u0131r\u0131n.<\/li>\n<li><strong>K\u00f6k neden<\/strong> \u2014 A\u011f\u0131r eklenti, tema, i\u00e7e aktarma i\u015flemi, bozuk kod veya yanl\u0131\u015f PHP-FPM ayar\u0131 aray\u0131n.<\/li>\n<li><strong>Sunucu izlemesi<\/strong> \u2014 RSS, swap, FPM s\u00fcre\u00e7leri, disk alan\u0131 ve loglar\u0131 birlikte takip edin.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">WordPress bellek s\u0131n\u0131r\u0131 hatas\u0131n\u0131 \u00e7\u00f6zmek i\u00e7in \u00f6nce PHP&#039;nin ger\u00e7ek memory_limit de\u011ferini ve hatay\u0131 \u00fcreten i\u015flemi belirleyin; ard\u0131ndan wp-config.php, php.ini veya .user.ini \u00fczerinden kontroll\u00fc bir art\u0131\u015f yap\u0131n. Belle\u011fi y\u00fckseltmek tek ba\u015f\u0131na yeterli de\u011fildir: a\u011f\u0131r eklenti, PHP-FPM s\u00fcre\u00e7 say\u0131s\u0131 ve VPS&#039;in toplam RAM kullan\u0131m\u0131 da \u00f6l\u00e7\u00fclmelidir.<\/p>\n<div class=\"aiw-toc\" style=\"border:1px solid #dbe3ea;border-radius:8px;padding:16px 20px;margin:0 0 28px\">\n<p class=\"aiw-toc-head\"><strong>\u0130\u00e7indekiler<\/strong><span class=\"aiw-toc-meta\"> \u00b7 11 dk okuma<\/span><\/p>\n<ol style=\"margin:10px 0 0;padding-left:22px\">\n<li><a href=\"#wordpress-bellek-siniri-hatasi-ne-anlama-gelir\">WordPress bellek s\u0131n\u0131r\u0131 hatas\u0131 ne anlama gelir?<\/a><\/li>\n<li><a href=\"#once-mevcut-php-bellek-sinirini-nasil-ogrenirsiniz\">\u00d6nce mevcut PHP bellek s\u0131n\u0131r\u0131n\u0131 nas\u0131l \u00f6\u011frenirsiniz?<\/a><\/li>\n<li><a href=\"#wp-config-php-ile-wordpress-bellek-siniri-artirilir-mi\">wp-config.php ile WordPress bellek s\u0131n\u0131r\u0131 art\u0131r\u0131l\u0131r m\u0131?<\/a><\/li>\n<li><a href=\"#php-memory_limit-degeri-nasil-artirilir\">PHP memory_limit de\u011feri nas\u0131l art\u0131r\u0131l\u0131r?<\/a><\/li>\n<li><a href=\"#hangi-eklenti-veya-tema-bellegi-tuketiyor\">Hangi eklenti veya tema belle\u011fi t\u00fcketiyor?<\/a><\/li>\n<li><a href=\"#php-fpm-surecleri-ve-sunucu-rami-nasil-kontrol-edilir\">PHP-FPM s\u00fcre\u00e7leri ve sunucu RAM&#039;i nas\u0131l kontrol edilir?<\/a><\/li>\n<li><a href=\"#256m-mi-512m-mi-deger-secimi-nasil-yapilir\">256M mi, 512M mi? De\u011fer se\u00e7imi nas\u0131l yap\u0131l\u0131r?<\/a><\/li>\n<li><a href=\"#wordpress-bellek-hatasi-devam-ederse-ne-kontrol-edilmeli\">WordPress bellek hatas\u0131 devam ederse ne kontrol edilmeli?<\/a><\/li>\n<li><a href=\"#kaynak-tuketimini-kalici-olarak-nasil-azaltirsiniz\">Kaynak t\u00fcketimini kal\u0131c\u0131 olarak nas\u0131l azalt\u0131rs\u0131n\u0131z?<\/a><\/li>\n<li><a href=\"#degisiklik-yapmadan-once-sunlari-kontrol-edin\">De\u011fi\u015fiklik Yapmadan \u00d6nce \u015eunlar\u0131 Kontrol Edin<\/a><\/li>\n<li><a href=\"#sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/a><\/li>\n<li><a href=\"#kaynaklar\">Kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n<h2 id=\"wordpress-bellek-siniri-hatasi-ne-anlama-gelir\">WordPress bellek s\u0131n\u0131r\u0131 hatas\u0131 ne anlama gelir?<\/h2>\n<p>WordPress bellek s\u0131n\u0131r\u0131 hatas\u0131, bir PHP iste\u011finin kendisine ayr\u0131lan <code>memory_limit<\/code> de\u011ferini a\u015fmas\u0131yla olu\u015fur. Ekranda genellikle <code>Allowed memory size of ... bytes exhausted<\/code> mesaj\u0131 g\u00f6r\u00fcn\u00fcr. D\u00fc\u015f\u00fck PHP belle\u011fi, a\u011f\u0131r bir eklenti, tema kodu, b\u00fcy\u00fck bir i\u015flem veya ayn\u0131 anda \u00e7al\u0131\u015fan PHP-FPM s\u00fcre\u00e7lerinin VPS kaynaklar\u0131n\u0131 t\u00fcketmesi bu hatay\u0131 tetikleyebilir.<\/p>\n<p>Bu mesaj do\u011frudan sunucuda RAM kalmad\u0131\u011f\u0131n\u0131 s\u00f6ylemez. PHP&#8217;nin tek bir istek i\u00e7in izin verilen \u00fcst s\u0131n\u0131r\u0131 a\u015f\u0131lm\u0131\u015f olabilir; i\u015fletim sisteminde h\u00e2l\u00e2 bo\u015f RAM bulunabilir. Bu ayr\u0131m\u0131 yapmadan yaln\u0131zca VPS RAM&#8217;ini art\u0131rmak, as\u0131l nedeni gizler.<\/p>\n<h3>Hata mesaj\u0131ndaki iki de\u011fer nas\u0131l okunur?<\/h3>\n<p>\u00d6rnek bir PHP hatas\u0131 \u015f\u00f6yle g\u00f6r\u00fcnebilir:<\/p>\n<pre><code>PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 40960 bytes)<\/code><\/pre>\n<p><code>268435456<\/code> bayt, 256 MiB de\u011ferine kar\u015f\u0131l\u0131k gelir. PHP 256 MiB s\u0131n\u0131r\u0131na ula\u015fm\u0131\u015f ve yaln\u0131zca 40 KiB daha ay\u0131rmaya \u00e7al\u0131\u015f\u0131rken i\u015flemi durdurmu\u015ftur. Buradaki <code>tried to allocate<\/code> de\u011feri toplam kullan\u0131lan belle\u011fi de\u011fil, son ba\u015far\u0131s\u0131z tahsisin boyutunu g\u00f6sterir.<\/p>\n<p>WordPress taraf\u0131ndaki <code>WP_MEMORY_LIMIT<\/code> ve <code>WP_MAX_MEMORY_LIMIT<\/code> sabitleri, PHP&#8217;nin izin verdi\u011fi de\u011ferin \u00fczerinde bir s\u0131n\u0131r olu\u015fturamaz. PHP yap\u0131land\u0131rmas\u0131ndaki <code>memory_limit<\/code> daha d\u00fc\u015f\u00fckse WordPress&#8217;in istedi\u011fi de\u011fer uygulanmayabilir.<\/p>\n<p><strong>Hemen kontrol edin<\/strong> &#8211; Hata mesaj\u0131ndaki byte de\u011ferini MiB&#8217;ye \u00e7evirin ve PHP&#8217;nin ger\u00e7ek <code>memory_limit<\/code> de\u011ferini ayr\u0131ca do\u011frulay\u0131n.<\/p>\n<h2 id=\"once-mevcut-php-bellek-sinirini-nasil-ogrenirsiniz\">\u00d6nce mevcut PHP bellek s\u0131n\u0131r\u0131n\u0131 nas\u0131l \u00f6\u011frenirsiniz?<\/h2>\n<p>WordPress y\u00f6netim panelinde <em>Ara\u00e7lar &gt; Site Sa\u011fl\u0131\u011f\u0131 &gt; Bilgi &gt; Sunucu<\/em> b\u00f6l\u00fcm\u00fcne giderek PHP s\u00fcr\u00fcm\u00fcn\u00fc ve bellek s\u0131n\u0131r\u0131n\u0131 g\u00f6rebilirsiniz. Paneldeki de\u011fer, web iste\u011fini kar\u015f\u0131layan PHP SAPI&#8217;sine aittir; SSH \u00fczerinden \u00e7al\u0131\u015ft\u0131r\u0131lan <code>php -i<\/code> \u00e7\u0131kt\u0131s\u0131yla her zaman ayn\u0131 olmayabilir.<\/p>\n<p>Komut sat\u0131r\u0131nda ilk kontrol i\u00e7in \u015fu komut kullan\u0131labilir:<\/p>\n<pre><code>php -r 'echo \"memory_limit=\" . ini_get(\"memory_limit\") . PHP_EOL;'<\/code><\/pre>\n<p>Bu komut CLI yap\u0131land\u0131rmas\u0131n\u0131 g\u00f6sterir. Web sitesi PHP-FPM kullan\u0131yorsa CLI ile FPM farkl\u0131 <code>php.ini<\/code> dosyalar\u0131ndan \u00e7al\u0131\u015fabilir.<\/p>\n<p>Debian ve Ubuntu tabanl\u0131 sistemlerde y\u00fckl\u00fc PHP s\u00fcr\u00fcmlerini g\u00f6rmek i\u00e7in:<\/p>\n<pre><code>php -v<br>php --ini<br>systemctl list-units --type=service 'php*-fpm.service'<\/code><\/pre>\n<p><code>php --ini<\/code> \u00e7\u0131kt\u0131s\u0131 ana yap\u0131land\u0131rma dosyas\u0131n\u0131n yolunu verir. FPM servisinin ad\u0131 s\u00fcr\u00fcme g\u00f6re <code>php8.2-fpm<\/code> veya <code>php8.3-fpm<\/code> olabilir. Servis ad\u0131n\u0131 varsaymak yerine <code>systemctl<\/code> \u00e7\u0131kt\u0131s\u0131yla do\u011frulamak gerekir.<\/p>\n<p>Web taraf\u0131ndaki ger\u00e7ek de\u011feri g\u00f6rmek i\u00e7in ge\u00e7ici bir PHP dosyas\u0131nda <code>ini_get('memory_limit')<\/code> kullan\u0131labilir. Dosyay\u0131 testten hemen sonra silin; <code>phpinfo()<\/code> \u00e7\u0131kt\u0131s\u0131 s\u00fcr\u00fcm, yol ve ortam bilgilerini gere\u011finden fazla a\u00e7\u0131\u011fa \u00e7\u0131karabilir.<\/p>\n<p>WordPress&#8217;in hangi s\u0131n\u0131r\u0131 kulland\u0131\u011f\u0131n\u0131 g\u00f6rmek i\u00e7in WP-CLI y\u00fckl\u00fcyse:<\/p>\n<pre><code>wp eval 'echo WP_MEMORY_LIMIT . PHP_EOL . WP_MAX_MEMORY_LIMIT . PHP_EOL;'<\/code><\/pre>\n<p>Komut, WordPress&#8217;in tan\u0131mlad\u0131\u011f\u0131 de\u011ferleri g\u00f6sterir. PHP&#8217;nin ger\u00e7ek s\u0131n\u0131r\u0131n\u0131 ayr\u0131ca incelemeden bu \u00e7\u0131kt\u0131y\u0131 tek ba\u015f\u0131na yeterli kabul etmeyin.<\/p>\n<p><strong>De\u011feri kar\u015f\u0131la\u015ft\u0131r\u0131n<\/strong> &#8211; CLI, PHP-FPM ve WordPress katmanlar\u0131n\u0131n bellek de\u011ferlerini ayr\u0131 ayr\u0131 kaydedin.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">\u0130pucu<\/p>\n<p>H\u0131zl\u0131 bir ilk ad\u0131m olarak WordPress Site Sa\u011fl\u0131\u011f\u0131 ekran\u0131ndaki PHP bellek s\u0131n\u0131r\u0131n\u0131, SSH \u00fczerinden \u00e7al\u0131\u015fan php -r komutunun \u00e7\u0131kt\u0131s\u0131yla kar\u015f\u0131la\u015ft\u0131r\u0131n. \u0130ki de\u011fer farkl\u0131ysa yanl\u0131\u015f PHP SAPI&#039;sini d\u00fczenliyor olabilirsiniz.<\/p>\n<\/div>\n<h2 id=\"wp-config-php-ile-wordpress-bellek-siniri-artirilir-mi\">wp-config.php ile WordPress bellek s\u0131n\u0131r\u0131 art\u0131r\u0131l\u0131r m\u0131?<\/h2>\n<p>WordPress&#8217;in <code>wp-config.php<\/code> dosyas\u0131nda iki sabit yayg\u0131n bi\u00e7imde kullan\u0131l\u0131r:<\/p>\n<pre><code>define( 'WP_MEMORY_LIMIT', '256M' );<br>define( 'WP_MAX_MEMORY_LIMIT', '512M' );<\/code><\/pre>\n<p><code>WP_MEMORY_LIMIT<\/code> normal site istekleri i\u00e7in, <code>WP_MAX_MEMORY_LIMIT<\/code> ise y\u00f6netim paneli ve baz\u0131 arka plan i\u015flemleri i\u00e7in hedef de\u011feri belirtir. Sat\u0131rlar\u0131, dosyadaki <code>That's all, stop editing!<\/code> yorumundan \u00f6nce ekleyin. Ayn\u0131 sabit daha \u00f6nce tan\u0131mlanm\u0131\u015fsa ikinci bir <code>define<\/code> sat\u0131r\u0131 eklemek yerine mevcut sat\u0131r\u0131 d\u00fczenleyin.<\/p>\n<p>Bu de\u011ferler sihirli bir RAM art\u0131\u015f\u0131 sa\u011flamaz. PHP&#8217;nin <code>memory_limit<\/code> de\u011feri 128M ise WordPress&#8217;in 512M istemesi \u00e7o\u011fu kurulumda etkili olmaz. Hosting sa\u011flay\u0131c\u0131s\u0131 veya PHP yap\u0131land\u0131rmas\u0131 <code>ini_set<\/code> kullan\u0131m\u0131n\u0131 da k\u0131s\u0131tlayabilir.<\/p>\n<p>Dosyay\u0131 de\u011fi\u015ftirmeden \u00f6nce yedek al\u0131n ve s\u00f6zdizimini do\u011frulay\u0131n. WP-CLI bulunan ortamlarda:<\/p>\n<pre><code>cp wp-config.php wp-config.php.bak<br>php -l wp-config.php<\/code><\/pre>\n<p><code>php -l<\/code> yaln\u0131zca PHP s\u00f6zdizimini kontrol eder; WordPress&#8217;in do\u011fru dosyadan y\u00fcklendi\u011fini garanti etmez. Yanl\u0131\u015f bir kopyay\u0131 d\u00fczenlememek i\u00e7in \u00f6nce sitenin k\u00f6k dizinini ve dosyan\u0131n sahipli\u011fini kontrol edin.<\/p>\n<p>WordPress&#8217;in resmi geli\u015ftirici belgelerinde bu sabitler i\u00e7in belirli bir evrensel de\u011fer \u00f6nerilmez. Siteye, eklentilere ve sunucu kapasitesine g\u00f6re \u00f6l\u00e7\u00fcm yapmak gerekir. 256M baz\u0131 i\u00e7erik sitelerinde yeterli olabilirken, g\u00f6rsel i\u015fleme veya b\u00fcy\u00fck i\u00e7e aktarma i\u015flemleri daha y\u00fcksek ge\u00e7ici bellek isteyebilir.<\/p>\n<p><strong>Dosyay\u0131 kontroll\u00fc de\u011fi\u015ftirin<\/strong> &#8211; \u00d6nce yedek al\u0131n, tek bir de\u011fer de\u011fi\u015ftirin ve y\u00f6netim panelindeki i\u015flemi yeniden deneyin.<\/p>\n<h2 id=\"php-memory_limit-degeri-nasil-artirilir\">PHP memory_limit de\u011feri nas\u0131l art\u0131r\u0131l\u0131r?<\/h2>\n<p>WordPress sabitleri etkili olmad\u0131\u011f\u0131nda PHP katman\u0131n\u0131 inceleyin. De\u011fi\u015fiklik y\u00f6ntemi, sunucunun PHP&#8217;yi Apache mod\u00fcl\u00fc, PHP-FPM veya farkl\u0131 bir panel arac\u0131l\u0131\u011f\u0131yla \u00e7al\u0131\u015ft\u0131rmas\u0131na g\u00f6re de\u011fi\u015fir.<\/p>\n<h3>php.ini \u00fczerinden ayarlama<\/h3>\n<p>PHP-FPM i\u00e7in kullan\u0131lan <code>php.ini<\/code> dosyas\u0131n\u0131 <code>php --ini<\/code> ile bulabilirsiniz; fakat bu komut CLI dosyas\u0131n\u0131 g\u00f6sterebilir. FPM yap\u0131land\u0131rma yolunu servis ve da\u011f\u0131t\u0131m belgeleriyle do\u011frulay\u0131n. Sat\u0131r \u00f6rne\u011fi:<\/p>\n<pre><code>memory_limit = 256M<\/code><\/pre>\n<p>De\u011fi\u015fiklikten sonra ilgili FPM servisini yeniden y\u00fckleyin veya yeniden ba\u015flat\u0131n:<\/p>\n<pre><code>sudo systemctl restart php8.2-fpm<br>sudo systemctl reload nginx<\/code><\/pre>\n<p>Buradaki PHP s\u00fcr\u00fcm\u00fcn\u00fc sisteminizde kurulu s\u00fcr\u00fcmle de\u011fi\u015ftirin. S\u00fcr\u00fcm\u00fc kontrol etmeden <code>php8.2-fpm<\/code> yazmak, olmayan bir servisi yeniden ba\u015flatmaya \u00e7al\u0131\u015f\u0131r.<\/p>\n<h3>.user.ini ve kontrol paneli<\/h3>\n<p>Payla\u015f\u0131ml\u0131 hosting veya s\u0131n\u0131rl\u0131 VPS ortamlar\u0131nda <code>.user.ini<\/code> dosyas\u0131 kullan\u0131labilir:<\/p>\n<pre><code>memory_limit = 256M<\/code><\/pre>\n<p>PHP-FPM, <code>.user.ini<\/code> de\u011fi\u015fikliklerini hemen okumayabilir. <code>user_ini.cache_ttl<\/code> de\u011ferine ba\u011fl\u0131 olarak birka\u00e7 dakika beklemek gerekebilir. cPanel, Plesk veya benzeri bir panel kullan\u0131l\u0131yorsa ayn\u0131 ayar\u0131n PHP se\u00e7enekleri ekran\u0131ndan yap\u0131lmas\u0131 daha g\u00fcvenlidir.<\/p>\n<p>Apache kullan\u0131lan baz\u0131 ortamlarda <code>.htaccess<\/code> i\u00e7inde <code>php_value memory_limit 256M<\/code> \u00e7al\u0131\u015fabilir; PHP-FPM veya CGI kurulumlar\u0131nda ise 500 hatas\u0131na yol a\u00e7abilir. Web sunucusunun \u00e7al\u0131\u015fma modelini bilmeden bu sat\u0131r\u0131 eklemeyin.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Dikkat<\/p>\n<p>wp-config.php i\u00e7ine ayn\u0131 define sat\u0131r\u0131n\u0131 iki kez eklemeyin. PHP-FPM kullan\u0131rken .htaccess i\u00e7ine php_value yazmak baz\u0131 kurulumlarda do\u011frudan 500 hatas\u0131 \u00fcretebilir.<\/p>\n<\/div>\n<h2 id=\"hangi-eklenti-veya-tema-bellegi-tuketiyor\">Hangi eklenti veya tema belle\u011fi t\u00fcketiyor?<\/h2>\n<p>Bellek s\u0131n\u0131r\u0131n\u0131 art\u0131rmak semptomu ge\u00e7ici olarak azaltabilir. Kal\u0131c\u0131 \u00e7\u00f6z\u00fcm i\u00e7in hatan\u0131n hangi istekte olu\u015ftu\u011funu bulmak gerekir. Yedekleme, g\u00f6rsel yeniden boyutland\u0131rma, XML\/CSV i\u00e7e aktarma, sayfa olu\u015fturucu ve e-ticaret eklentileri b\u00fcy\u00fck veri k\u00fcmeleriyle \u00e7al\u0131\u015fabilir.<\/p>\n<p>\u00d6nce WordPress hata g\u00fcnl\u00fc\u011f\u00fcn\u00fc kontroll\u00fc bi\u00e7imde a\u00e7\u0131n:<\/p>\n<pre><code>define( 'WP_DEBUG', true );<br>define( 'WP_DEBUG_LOG', true );<br>define( 'WP_DEBUG_DISPLAY', false );<\/code><\/pre>\n<p>Hatalar genellikle <code>wp-content\/debug.log<\/code> dosyas\u0131na yaz\u0131l\u0131r. \u00dcretim sitesinde <code>WP_DEBUG_DISPLAY<\/code> de\u011ferini <code>true<\/code> yapmak hata ayr\u0131nt\u0131lar\u0131n\u0131 ziyaret\u00e7ilere g\u00f6sterebilir. Test tamamlan\u0131nca hata ay\u0131klamay\u0131 kapat\u0131n veya loglama politikan\u0131za g\u00f6re y\u00f6netin.<\/p>\n<p>Log i\u00e7inde eklenti veya tema yolunu aray\u0131n:<\/p>\n<pre><code>grep -nEi 'Allowed memory size|memory exhausted|wp-content\/plugins|wp-content\/themes' wp-content\/debug.log | tail -n 50<\/code><\/pre>\n<p>\u00d6rne\u011fin <code>\/wp-content\/plugins\/example-plugin\/<\/code> yolu tekrar tekrar g\u00f6r\u00fcn\u00fcyorsa eklenti g\u00fc\u00e7l\u00fc bir adayd\u0131r; yine de tek sat\u0131r\u0131n kesin k\u00f6k neden oldu\u011funu varsaymay\u0131n. Ayn\u0131 i\u015flem bir cron g\u00f6revi, REST iste\u011fi veya y\u00f6netim paneli \u00e7a\u011fr\u0131s\u0131 taraf\u0131ndan tetikleniyor olabilir.<\/p>\n<p>\u0130zolasyon i\u00e7in staging ortam\u0131nda eklentileri tek tek devre d\u0131\u015f\u0131 b\u0131rak\u0131n. WP-CLI ile:<\/p>\n<pre><code>wp plugin list --status=active<br>wp plugin deactivate eklenti-klasoru<\/code><\/pre>\n<p>\u00dcretim ortam\u0131nda t\u00fcm eklentileri bir anda kapatmak \u00f6deme, \u00f6nbellek veya g\u00fcvenlik katmanlar\u0131n\u0131 bozabilir. \u00d6nce snapshot ya da do\u011frulanm\u0131\u015f yedek al\u0131n; ard\u0131ndan k\u0131sa bir bak\u0131m penceresi planlay\u0131n.<\/p>\n<p>WordPress i\u00e7in VPS kurulum ad\u0131mlar\u0131n\u0131 incelerken PHP s\u00fcr\u00fcm\u00fc, FPM servisi ve dosya sahipli\u011fini de ayn\u0131 tabloya ekleyin. Yaln\u0131zca uygulama katman\u0131n\u0131 de\u011fi\u015ftirip i\u015fletim sistemi kaynaklar\u0131n\u0131 izlememek te\u015fhisi eksik b\u0131rak\u0131r.<\/p>\n<p><strong>\u0130zolasyon testi yap\u0131n<\/strong> &#8211; Eklenti ve temay\u0131 staging ortam\u0131nda s\u0131rayla devre d\u0131\u015f\u0131 b\u0131rak\u0131p her ad\u0131mda ayn\u0131 iste\u011fi yeniden \u00e7al\u0131\u015ft\u0131r\u0131n.<\/p>\n<h2 id=\"php-fpm-surecleri-ve-sunucu-rami-nasil-kontrol-edilir\">PHP-FPM s\u00fcre\u00e7leri ve sunucu RAM&#8217;i nas\u0131l kontrol edilir?<\/h2>\n<p>PHP&#8217;nin tek istek s\u0131n\u0131r\u0131 ile VPS&#8217;in toplam RAM&#8217;i farkl\u0131 konulard\u0131r. PHP-FPM&#8217;de <code>pm.max_children<\/code> de\u011feri ayn\u0131 anda \u00e7al\u0131\u015fabilecek PHP s\u00fcre\u00e7lerinin say\u0131s\u0131n\u0131 s\u0131n\u0131rlar. Her s\u00fcrecin ger\u00e7ek RSS belle\u011fi \u00f6l\u00e7\u00fclmeden y\u00fcksek bir de\u011fer vermek swap kullan\u0131m\u0131na ve 502 hatalar\u0131na yol a\u00e7abilir.<\/p>\n<pre><code>free -h<br>ps -eo pid,ppid,rss,cmd --sort=-rss | head -n 15<br>systemctl status php8.2-fpm --no-pager<\/code><\/pre>\n<p><code>rss<\/code> de\u011feri KiB cinsindendir. \u00d6rne\u011fin en yo\u011fun 10 PHP s\u00fcrecinin her biri yakla\u015f\u0131k 180 MiB kullan\u0131yorsa <code>pm.max_children = 20<\/code> teorik olarak 3,6 GiB civar\u0131nda bellek isteyebilir; i\u015fletim sistemi, veritaban\u0131 ve web sunucusu i\u00e7in ayr\u0131lacak pay buna dahil de\u011fildir.<\/p>\n<p>PHP-FPM havuzu i\u00e7in kaba bir kapasite hesab\u0131 yap\u0131labilir:<\/p>\n<pre><code>G\u00fcvenli max_children \u2248 PHP'ye ayr\u0131labilir RAM \/ bir PHP s\u00fcrecinin ortalama RSS de\u011feri<\/code><\/pre>\n<p>Bu yaln\u0131zca ba\u015flang\u0131\u00e7 tahminidir. Yo\u011fun saatlerde <code>ps<\/code>, FPM durum metrikleri ve monitoring verileriyle do\u011frulanmal\u0131d\u0131r. <code>free -h<\/code> \u00e7\u0131kt\u0131s\u0131nda kullan\u0131labilir bellek d\u00fc\u015f\u00fcyor, swap s\u00fcrekli b\u00fcy\u00fcyor veya kernel loglar\u0131nda OOM mesajlar\u0131 g\u00f6r\u00fcl\u00fcyorsa yaln\u0131zca <code>memory_limit<\/code> art\u0131rmak do\u011fru yakla\u015f\u0131m de\u011fildir.<\/p>\n<p>Linux i\u015flem kaynaklar\u0131n\u0131 incelemek i\u00e7in <strong><a href=\"https:\/\/www.vps.tc\/blog\/tr\/linux-islem-yonetimi-ps-top-kill\/\">Linux&#8217;ta \u0130\u015flem Y\u00f6netimi: ps, top ve kill Kullan\u0131m\u0131<\/a><\/strong> yaz\u0131s\u0131ndaki komutlardan yararlanabilirsiniz. Bellek bask\u0131s\u0131 s\u0131ras\u0131nda rastgele <code>kill -9<\/code> \u00e7al\u0131\u015ft\u0131rmak yerine \u00f6nce hangi servisin s\u00fcre\u00e7 \u00fcretti\u011fini belirleyin.<\/p>\n<h2 id=\"256m-mi-512m-mi-deger-secimi-nasil-yapilir\">256M mi, 512M mi? De\u011fer se\u00e7imi nas\u0131l yap\u0131l\u0131r?<\/h2>\n<p>Her WordPress kurulumu i\u00e7in ge\u00e7erli tek bir bellek de\u011feri yoktur. De\u011fer se\u00e7erken sitenin normal sayfa iste\u011fiyle a\u011f\u0131r y\u00f6netim i\u015flemini ay\u0131r\u0131n.<\/p>\n<table>\n<thead>\n<tr>\n<th>Durum<\/th>\n<th>Ba\u015flang\u0131\u00e7 yakla\u015f\u0131m\u0131<\/th>\n<th>Kontrol<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Basit kurumsal site<\/td>\n<td>128M-256M<\/td>\n<td>PHP loglar\u0131 ve y\u00f6netim paneli i\u015flemleri<\/td>\n<\/tr>\n<tr>\n<td>Yo\u011fun eklenti kullanan site<\/td>\n<td>256M civar\u0131n\u0131 \u00f6l\u00e7erek de\u011ferlendirme<\/td>\n<td>Aktif eklenti, FPM RSS ve hata s\u0131kl\u0131\u011f\u0131<\/td>\n<\/tr>\n<tr>\n<td>WooCommerce veya b\u00fcy\u00fck katalog<\/td>\n<td>256M-512M ihtiyaca g\u00f6re<\/td>\n<td>\u00dcr\u00fcn i\u00e7e aktarma ve y\u00f6netim i\u015flemleri<\/td>\n<\/tr>\n<tr>\n<td>B\u00fcy\u00fck i\u00e7e aktarma<\/td>\n<td>Kal\u0131c\u0131 yerine ge\u00e7ici art\u0131\u015f<\/td>\n<td>\u0130\u015flem tamamland\u0131ktan sonra log ve RAM kullan\u0131m\u0131<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Tablodaki aral\u0131klar zorunlu gereksinim de\u011fil, te\u015fhis i\u00e7in ba\u015flang\u0131\u00e7 noktas\u0131d\u0131r. WordPress, PHP veya bir eklenti i\u00e7in <code>512M her zaman gereklidir<\/code> \u015feklinde genel bir kural bulunmaz.<\/p>\n<p>\u00d6rne\u011fin yaln\u0131zca medya y\u00fckleme s\u0131ras\u0131nda hata al\u0131n\u0131yorsa g\u00f6rsel boyutlar\u0131, ImageMagick\/GD i\u015flemleri ve PHP \u00e7al\u0131\u015fma s\u00fcresi birlikte incelenmelidir. Y\u00f6netim panelinde sorun yokken \u00f6n y\u00fczde hata varsa tema \u015fablonu, sorgu say\u0131s\u0131 veya cache katman\u0131 daha olas\u0131 adaylard\u0131r.<\/p>\n<p><strong>Art\u0131\u015f\u0131 \u00f6l\u00e7erek s\u0131n\u0131rlay\u0131n<\/strong> &#8211; Belle\u011fi bir anda 1G yapmay\u0131n; k\u00fc\u00e7\u00fck bir art\u0131\u015ftan sonra RSS, swap ve hata loglar\u0131n\u0131 yeniden de\u011ferlendirin.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">\u00d6rnek<\/p>\n<p>Bir \u00fcr\u00fcn i\u00e7e aktarma i\u015flemi yaln\u0131zca y\u00f6netim panelinde hata veriyor, \u00f6n y\u00fcz normal \u00e7al\u0131\u015f\u0131yorsa WP_MAX_MEMORY_LIMIT ve i\u00e7e aktarma eklentisinin loglar\u0131 birlikte incelenmelidir. FPM havuzunu b\u00fcy\u00fctmeden \u00f6nce i\u015flemi par\u00e7alara b\u00f6lmek daha d\u00fc\u015f\u00fck riskli olabilir.<\/p>\n<\/div>\n<h2 id=\"wordpress-bellek-hatasi-devam-ederse-ne-kontrol-edilmeli\">WordPress bellek hatas\u0131 devam ederse ne kontrol edilmeli?<\/h2>\n<p>De\u011fer art\u0131r\u0131ld\u0131\u011f\u0131 halde hata s\u00fcr\u00fcyorsa a\u015fa\u011f\u0131daki katmanlar\u0131 s\u0131rayla inceleyin:<\/p>\n<ul>\n<li><strong>Yanl\u0131\u015f PHP SAPI:<\/strong> CLI&#8217;da 512M g\u00f6r\u00fcn\u00fcrken PHP-FPM 128M ile \u00e7al\u0131\u015f\u0131yor olabilir.<\/li>\n<li><strong>Yanl\u0131\u015f dosya:<\/strong> Birden fazla WordPress kurulumu veya staging dizini bulunabilir.<\/li>\n<li><strong>Yap\u0131land\u0131rma k\u0131s\u0131t\u0131:<\/strong> Hosting hesab\u0131, PHP direktifini de\u011fi\u015ftirmeyi engelleyebilir.<\/li>\n<li><strong>PHP s\u00fcr\u00fcm\u00fc:<\/strong> Eklenti gereksinimleri ve kullan\u0131lan uzant\u0131lar s\u00fcr\u00fcmle uyumsuz olabilir.<\/li>\n<li><strong>Ger\u00e7ek RAM bask\u0131s\u0131:<\/strong> FPM, MariaDB ve web sunucusu ayn\u0131 anda belle\u011fi t\u00fcketebilir.<\/li>\n<li><strong>Bozuk kod:<\/strong> Sonsuz d\u00f6ng\u00fc veya s\u0131n\u0131rs\u0131z dizi b\u00fcy\u00fcmesi bellek limitini h\u0131zla doldurabilir.<\/li>\n<\/ul>\n<p>Nginx loglar\u0131, PHP-FPM loglar\u0131 ve WordPress logunu ayn\u0131 zaman aral\u0131\u011f\u0131nda kar\u015f\u0131la\u015ft\u0131r\u0131n. HTTP 502 g\u00f6r\u00fcl\u00fcyorsa yaln\u0131zca WordPress&#8217;e odaklanmay\u0131n; upstream PHP-FPM s\u00fcrecinin \u00f6ld\u00fcr\u00fclmesi veya zaman a\u015f\u0131m\u0131 da ara\u015ft\u0131r\u0131lmal\u0131d\u0131r. Bu ayr\u0131m\u0131 <strong><a href=\"https:\/\/www.vps.tc\/blog\/tr\/502-bad-gateway-hatasi-nedir-nasil-cozulur\/\">502 Bad Gateway Hatas\u0131 Nedir ve Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr?<\/a><\/strong> ba\u015fl\u0131\u011f\u0131ndaki katman yakla\u015f\u0131m\u0131yla birlikte de\u011ferlendirebilirsiniz.<\/p>\n<p>Disk alan\u0131 da kontrol edilmelidir. Log yaz\u0131lamayan, ge\u00e7ici dosya olu\u015fturamayan veya inode&#8217;lar\u0131 t\u00fckenen bir sistem farkl\u0131 belirtiler \u00fcretebilir:<\/p>\n<pre><code>df -h<br>df -i<br>journalctl -u php8.2-fpm --since \"1 hour ago\" --no-pager<\/code><\/pre>\n<p>Disk dolulu\u011fu bellek hatas\u0131n\u0131n kendisi de\u011fildir; fakat te\u015fhis loglar\u0131n\u0131n kaybolmas\u0131na ve PHP s\u00fcre\u00e7lerinin beklenmedik davranmas\u0131na neden olabilir.<\/p>\n<p><strong>Katmanlar\u0131 ay\u0131r\u0131n<\/strong> &#8211; WordPress, PHP-FPM, web sunucusu, i\u015fletim sistemi ve disk durumunu ayn\u0131 zaman aral\u0131\u011f\u0131nda kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">Sahadan not<\/p>\n<p>Evdeki ThinkPad T480 \u00fczerinde \u00e7al\u0131\u015fan test ortam\u0131 bir yaz ak\u015fam\u0131 yava\u015flay\u0131nca \u00f6nce PHP s\u00fcre\u00e7lerine bakt\u0131m. Grafana&#039;da s\u0131cakl\u0131\u011f\u0131n basamak basamak y\u00fckseldi\u011fini, CPU frekans\u0131n\u0131n d\u00fc\u015ft\u00fc\u011f\u00fcn\u00fc ve RSS de\u011ferlerinin normal kald\u0131\u011f\u0131n\u0131 g\u00f6rd\u00fcm; fan ar\u0131zas\u0131 nedeniyle termal k\u0131s\u0131tlama devreye girmi\u015fti. O g\u00fcnden beri kaynak te\u015fhisinde bellek grafi\u011fini CPU s\u0131cakl\u0131\u011f\u0131 ve disk I\/O ile ayn\u0131 zaman aral\u0131\u011f\u0131nda kar\u015f\u0131la\u015ft\u0131r\u0131yorum.<\/p>\n<\/div>\n<h2 id=\"kaynak-tuketimini-kalici-olarak-nasil-azaltirsiniz\">Kaynak t\u00fcketimini kal\u0131c\u0131 olarak nas\u0131l azalt\u0131rs\u0131n\u0131z?<\/h2>\n<p>Kal\u0131c\u0131 \u00e7\u00f6z\u00fcm \u00e7o\u011fu zaman daha b\u00fcy\u00fck bir say\u0131 yazmak de\u011fil, a\u011f\u0131r i\u015flemi k\u00fc\u00e7\u00fcltmektir. Kullan\u0131lmayan eklentileri kald\u0131r\u0131n; yaln\u0131zca devre d\u0131\u015f\u0131 b\u0131rakmak, dosyalar\u0131 ve g\u00fcncelleme y\u00fck\u00fcn\u00fc sistemden silmez. Eklentileri g\u00fcncel tutun, fakat g\u00fcncellemeyi \u00f6nce staging ortam\u0131nda test edin.<\/p>\n<p>G\u00f6rselleri y\u00fcklemeden \u00f6nce uygun boyuta indirin. B\u00fcy\u00fck CSV i\u00e7e aktarmalar\u0131n\u0131 tek bir dev PHP iste\u011fi yerine par\u00e7alara b\u00f6l\u00fcn. WP-Cron yo\u011fun \u00e7al\u0131\u015f\u0131yorsa ger\u00e7ek sistem cron&#8217;u ile kontroll\u00fc bir zamanlama kullanmay\u0131 ve ayn\u0131 g\u00f6revin paralel \u00e7al\u0131\u015fmas\u0131n\u0131 engellemeyi de\u011ferlendirin.<\/p>\n<p>Sayfa cache&#8217;i, PHP OPcache ve veritaban\u0131 sorgu analizi de \u00f6nemlidir. Cache kurmadan TTFB de\u011ferini milisaniye hassasiyetinde tart\u0131\u015fmak, as\u0131l y\u00fck\u00fc yanl\u0131\u015f yerde aramakt\u0131r. Cache kullan\u0131m\u0131 bellek hatas\u0131n\u0131 her zaman \u00e7\u00f6zmez; tekrarlanan PHP isteklerini azaltarak s\u00fcre\u00e7 ba\u015f\u0131na bask\u0131y\u0131 d\u00fc\u015f\u00fcrebilir.<\/p>\n<p>VPS kaynaklar\u0131 yetersizse CPU, RAM, disk I\/O ve swap verilerini birlikte izleyin. Sadece RAM y\u00fckseltmek, hatal\u0131 bir eklentinin her istekte b\u00fcy\u00fcyen belle\u011fini d\u00fczeltmez. Uygulama davran\u0131\u015f\u0131 d\u00fczeltilmeden daha b\u00fcy\u00fck sunucuya ta\u015f\u0131nan sorun, bir s\u00fcre sonra daha pahal\u0131 bi\u00e7imde geri d\u00f6ner.<\/p>\n<p>Bir bellek de\u011fi\u015fikli\u011finden sonra en az\u0131ndan yo\u011fun saatleri kapsayan monitoring verisini saklay\u0131n. Uptime Kuma eri\u015filebilirli\u011fi g\u00f6sterir; PHP-FPM s\u00fcre\u00e7 say\u0131s\u0131, RAM ve swap i\u00e7in Prometheus gibi metrik kaynaklar\u0131 gerekir.<\/p>\n<h2 id=\"degisiklik-yapmadan-once-sunlari-kontrol-edin\">De\u011fi\u015fiklik Yapmadan \u00d6nce \u015eunlar\u0131 Kontrol Edin<\/h2>\n<ul class=\"aiw-checklist\">\n<li>Hata mesaj\u0131ndaki toplam bellek de\u011ferini MiB olarak hesaplay\u0131n.<\/li>\n<li>CLI ile PHP-FPM bellek de\u011ferlerinin ayn\u0131 olup olmad\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n.<\/li>\n<li>wp-config.php dosyas\u0131n\u0131 d\u00fczenlemeden \u00f6nce yedekleyin.<\/li>\n<li>Hatan\u0131n olu\u015ftu\u011fu eklenti, tema veya i\u015flemi loglardan belirleyin.<\/li>\n<li>De\u011fi\u015fikli\u011fi \u00f6nce staging ortam\u0131nda test edin.<\/li>\n<li>PHP-FPM s\u00fcre\u00e7lerinin RSS, swap ve toplam RAM kullan\u0131m\u0131n\u0131 izleyin.<\/li>\n<li>\u0130\u015flem tamamlan\u0131nca debug loglamas\u0131n\u0131 ve ge\u00e7ici bellek art\u0131\u015f\u0131n\u0131 g\u00f6zden ge\u00e7irin.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>Bir sonraki bellek hatas\u0131nda yaln\u0131zca limiti y\u00fckseltmek yerine PHP-FPM, eklenti loglar\u0131 ve VPS metriklerini ayn\u0131 zaman \u00e7izelgesinde inceleyin. Tek bir \u00f6l\u00e7\u00fcm, genellikle do\u011fru katman\u0131 bulmak i\u00e7in yeterlidir.<\/p>\n<p class=\"aiw-cta-action\"><a href=\"https:\/\/www.vps.tc\/tr\/vps\">VPS paketlerini inceleyin<\/a><\/p>\n<\/div>\n<h2 id=\"sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/h2>\n<div class=\"aiw-faq\">\n<details class=\"aiw-faq-item\" open>\n<summary>WordPress bellek s\u0131n\u0131r\u0131 hatas\u0131 neden olur?<\/summary>\n<p>PHP taraf\u0131ndan bir iste\u011fe ayr\u0131lan memory_limit de\u011feri a\u015f\u0131ld\u0131\u011f\u0131nda olu\u015fur. A\u011f\u0131r eklentiler, b\u00fcy\u00fck g\u00f6rsel i\u015flemleri, i\u00e7e aktarma g\u00f6revleri, tema kodu, sonsuz d\u00f6ng\u00fcler ve y\u00fcksek PHP-FPM y\u00fck\u00fc yayg\u0131n nedenlerdir. Mesaj, tek ba\u015f\u0131na VPS RAM&#039;inin tamamen t\u00fckendi\u011fini kan\u0131tlamaz; PHP limitini ve sistem RAM&#039;ini ayr\u0131 ayr\u0131 kontrol etmek gerekir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>WordPress memory limit nas\u0131l art\u0131r\u0131l\u0131r?<\/summary>\n<p>\u00d6nce PHP-FPM&#039;in ger\u00e7ek memory_limit de\u011ferini belirleyin. Ard\u0131ndan wp-config.php i\u00e7inde WP_MEMORY_LIMIT ve gerekirse WP_MAX_MEMORY_LIMIT de\u011ferlerini d\u00fczenleyin. PHP s\u0131n\u0131r\u0131 d\u00fc\u015f\u00fck kal\u0131yorsa php.ini, .user.ini veya hosting panelinden memory_limit de\u011ferini art\u0131r\u0131n. De\u011fi\u015fiklikten sonra ilgili PHP-FPM servisini yeniden y\u00fckleyin ve y\u00f6netim panelindeki de\u011feri tekrar do\u011frulay\u0131n.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>WordPress i\u00e7in 256M bellek yeterli mi?<\/summary>\n<p>Basit bir kurumsal site i\u00e7in 128M veya 256M yeterli olabilir; fakat bu evrensel bir kural de\u011fildir. WooCommerce, b\u00fcy\u00fck kataloglar, sayfa olu\u015fturucular ve i\u00e7e aktarma i\u015flemleri daha fazla bellek isteyebilir. De\u011feri rastgele y\u00fckseltmek yerine hata loglar\u0131n\u0131, PHP-FPM s\u00fcre\u00e7lerinin RSS kullan\u0131m\u0131n\u0131 ve yo\u011fun saatlerdeki swap durumunu \u00f6l\u00e7\u00fcn.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>wp-config.php dosyas\u0131nda hangi bellek ayar\u0131 kullan\u0131l\u0131r?<\/summary>\n<p>Normal WordPress istekleri i\u00e7in WP_MEMORY_LIMIT, y\u00f6netim paneli ve baz\u0131 arka plan i\u015flemleri i\u00e7in WP_MAX_MEMORY_LIMIT kullan\u0131l\u0131r. \u00d6rnek de\u011ferler 256M ve 512M olabilir; PHP&#039;nin memory_limit de\u011feri daha d\u00fc\u015f\u00fckse WordPress bu s\u0131n\u0131r\u0131 a\u015famaz. Ayn\u0131 sabiti iki kez tan\u0131mlamay\u0131n ve de\u011fi\u015fiklikten \u00f6nce dosyan\u0131n yede\u011fini al\u0131n.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Bellek s\u0131n\u0131r\u0131n\u0131 art\u0131rd\u0131\u011f\u0131m halde hata neden devam ediyor?<\/summary>\n<p>Web sitesi PHP-FPM ile \u00e7al\u0131\u015f\u0131rken yaln\u0131zca CLI yap\u0131land\u0131rmas\u0131n\u0131 de\u011fi\u015ftirmi\u015f olabilirsiniz. Yanl\u0131\u015f WordPress kurulumu, hosting k\u0131s\u0131t\u0131, bozuk eklenti, ger\u00e7ek RAM bask\u0131s\u0131 veya PHP-FPM s\u00fcre\u00e7lerinin \u00f6ld\u00fcr\u00fclmesi de hatay\u0131 s\u00fcrd\u00fcrebilir. PHP-FPM loglar\u0131n\u0131, WordPress debug.log dosyas\u0131n\u0131, free -h \u00e7\u0131kt\u0131s\u0131n\u0131 ve web sunucusu loglar\u0131n\u0131 ayn\u0131 zaman aral\u0131\u011f\u0131nda kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>PHP-FPM ayarlar\u0131 WordPress bellek hatas\u0131n\u0131 etkiler mi?<\/summary>\n<p>Evet. memory_limit tek bir PHP iste\u011finin \u00fcst s\u0131n\u0131r\u0131d\u0131r; pm.max_children ise ayn\u0131 anda \u00e7al\u0131\u015fabilecek PHP-FPM s\u00fcre\u00e7lerini etkiler. Her s\u00fcre\u00e7 y\u00fcksek RSS kullan\u0131yorsa fazla say\u0131da child s\u00fcre\u00e7 toplam RAM&#039;i t\u00fcketebilir, swap ve 502 hatalar\u0131 olu\u015fabilir. Bu nedenle FPM s\u00fcre\u00e7 say\u0131s\u0131n\u0131 art\u0131rmadan \u00f6nce s\u00fcre\u00e7 ba\u015f\u0131na RSS, VPS RAM&#039;i ve veritaban\u0131 kullan\u0131m\u0131n\u0131 \u00f6l\u00e7\u00fcn.<\/p>\n<\/details>\n<\/div>\n<h2 id=\"kaynaklar\">Kaynaklar<\/h2>\n<ul class=\"aiw-sources\">\n<li><a href=\"https:\/\/developer.wordpress.org\/apis\/wp-config-php\/\" target=\"_blank\" rel=\"noopener\">WordPress Developer Resources &#8211; wp-config.php<\/a> \u2014 developer.wordpress.org<\/li>\n<li><a href=\"https:\/\/developer.wordpress.org\/advanced-administration\/debug\/debug-wordpress\/\" target=\"_blank\" rel=\"noopener\">WordPress Developer Resources &#8211; Debugging WordPress<\/a> \u2014 developer.wordpress.org<\/li>\n<li><a href=\"https:\/\/www.php.net\/manual\/en\/ini.core.php\" target=\"_blank\" rel=\"noopener\">PHP Manual &#8211; Core php.ini Directives<\/a> \u2014 php.net<\/li>\n<li><a href=\"https:\/\/www.php.net\/manual\/en\/install.fpm.configuration.php\" target=\"_blank\" rel=\"noopener\">PHP Manual &#8211; PHP-FPM Configuration<\/a> \u2014 php.net<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>WordPress bellek s\u0131n\u0131r\u0131 hatas\u0131n\u0131n nedenlerini PHP, wp-config.php ve PHP-FPM katmanlar\u0131nda inceleyin; g\u00fcvenli bellek art\u0131rma ve kal\u0131c\u0131 \u00e7\u00f6z\u00fcm ad\u0131mlar\u0131n\u0131 uygulay\u0131n.<\/p>\n","protected":false},"author":2,"featured_media":848,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[666],"tags":[],"class_list":["post-850","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cms"],"lang":"tr","translations":{"tr":850,"en":851},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/850","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/comments?post=850"}],"version-history":[{"count":1,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/850\/revisions"}],"predecessor-version":[{"id":852,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/850\/revisions\/852"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/848"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=850"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=850"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=850"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}