{"id":2167,"date":"2026-06-04T14:25:14","date_gmt":"2026-06-04T11:25:14","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=2167"},"modified":"2026-08-02T12:09:57","modified_gmt":"2026-08-02T12:09:57","slug":"wordpress-maksimum-calisma-suresi-asildi-hatasi-nasil-cozulur","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/tr\/wordpress-maksimum-calisma-suresi-asildi-hatasi-nasil-cozulur\/","title":{"rendered":"WordPress’te Maksimum \u00c7al\u0131\u015fma S\u00fcresi A\u015f\u0131ld\u0131 Hatas\u0131 Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr?"},"content":{"rendered":"

Binlerce \u00fcr\u00fcn\u00fc i\u00e7e aktaran bir WordPress i\u015flemi, belirli noktada \u201cMaximum execution time exceeded\u201d hatas\u0131yla durabilir. PHP s\u00fcresini b\u00fcy\u00fck bir de\u011fere \u00e7\u0131karmak i\u015flemi biraz daha ilerletse bile tek par\u00e7a sorgu, k\u0131sa proxy timeout’u veya yava\u015f d\u0131\u015f API \u00e7a\u011fr\u0131s\u0131 sorunu yeniden \u00fcretir.<\/p>\n

\u00d6nce hangi i\u015flem ba\u011flam\u0131n\u0131n s\u00fcreyi a\u015ft\u0131\u011f\u0131n\u0131 ve son ba\u015far\u0131l\u0131 birimi belirleyin. G\u00fcvenilir \u00e7\u00f6z\u00fcm \u00e7o\u011fu zaman s\u0131n\u0131rs\u0131z web iste\u011fi de\u011fil; parti, devam noktas\u0131, arka plan worker’\u0131 veya WP-CLI gibi kesintiden sonra g\u00fcvenle s\u00fcrd\u00fcr\u00fclebilen y\u00f6ntemdir.<\/p>\n

\u0130\u00e7indekiler<\/strong><\/p>\n
    \n
  1. Maksimum \u00e7al\u0131\u015fma s\u00fcresi nedir?<\/a><\/li>\n
  2. Ger\u00e7ek\u00e7i bir WordPress \u00f6rne\u011fi<\/a><\/li>\n
  3. Limit ne zaman art\u0131r\u0131lmal\u0131?<\/a><\/li>\n
  4. Yeni ba\u015flayanlar i\u00e7in tan\u0131 ad\u0131mlar\u0131<\/a><\/li>\n
  5. \u0130leri teknik yakla\u015f\u0131m<\/a><\/li>\n
  6. Riskler, s\u0131k hatalar ve rollback<\/a><\/li>\n
  7. AIOWS PHP Limitleri nas\u0131l yard\u0131mc\u0131 olur?<\/a><\/li>\n
  8. \u0130lgili AIOWS yaz\u0131lar\u0131<\/a><\/li>\n
  9. Sonu\u00e7 ve \u00f6nerilen yol<\/a><\/li>\n
  10. Resm\u00ee kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n

    Maksimum \u00e7al\u0131\u015fma s\u00fcresi nedir?<\/h2>\n

    max_execution_time<\/code>, PHP kodunun ne kadar s\u00fcre \u00e7al\u0131\u015fabilece\u011fini belirleyen s\u0131n\u0131rlardan biridir. Ger\u00e7ek istek ayr\u0131ca web sunucusu, reverse proxy, PHP-FPM, CDN, veritaban\u0131, uzak API veya istemci timeout’u nedeniyle daha erken kesilebilir.<\/p>\n

    Hata tek bir PHP \u00e7al\u0131\u015fmas\u0131n\u0131n s\u0131n\u0131r\u0131 a\u015ft\u0131\u011f\u0131n\u0131 g\u00f6sterir; hangi limitin de\u011fi\u015ftirilmesi gerekti\u011fini veya i\u015fin daha uzun s\u00fcre g\u00fcvenle \u00e7al\u0131\u015faca\u011f\u0131n\u0131 kan\u0131tlamaz. wp-admin, AJAX\/REST, cron, kuyruk worker’\u0131 ve WP-CLI farkl\u0131 yap\u0131land\u0131rma ba\u011flamlar\u0131 kullanabilir.<\/p>\n

    Ger\u00e7ek\u00e7i bir WordPress \u00f6rne\u011fi<\/h2>\n

    \u00dcr\u00fcn i\u00e7e aktarma i\u015flemi \u00fc\u00e7 bin sat\u0131rdan sonra 30 saniyelik PHP limitine ula\u015f\u0131yor. Limit 120 saniyeye \u00e7\u0131kar\u0131ld\u0131\u011f\u0131nda daha fazla \u00fcr\u00fcn i\u015fleniyor, ancak proxy 60 saniyede ba\u011flant\u0131y\u0131 kapat\u0131yor ve i\u015flem kald\u0131\u011f\u0131 yeri g\u00fcvenilir bi\u00e7imde bilmiyor.<\/p>\n

    Ekip i\u00e7e aktar\u0131c\u0131n\u0131n parti ve devam se\u00e7ene\u011fini kullan\u0131yor. Her parti i\u015flenen kimlikleri kaydediyor; kontroll\u00fc bir kesintiden sonra tamamlanan \u00fcr\u00fcnleri yinelemeden devam edebildi\u011fi do\u011frulan\u0131yor. PHP s\u00fcresi yaln\u0131z tek partinin ger\u00e7ek ihtiyac\u0131na g\u00f6re \u00f6l\u00e7\u00fcl\u00fc bi\u00e7imde ayarlan\u0131yor.<\/p>\n

    Limit ne zaman art\u0131r\u0131lmal\u0131?<\/h2>\n

    \u0130\u015fin kapsam\u0131 a\u00e7\u0131k\u00e7a s\u0131n\u0131rl\u0131ysa, tamamlanmaya do\u011fru \u00f6l\u00e7\u00fclebilir bi\u00e7imde ilerliyorsa ve desteklenen daha g\u00fcvenli bir b\u00f6lme y\u00f6ntemi yoksa \u00e7al\u0131\u015fma s\u00fcresi \u00f6l\u00e7\u00fcl\u00fc bi\u00e7imde art\u0131r\u0131labilir. \u0130stenen de\u011fer, hosting tavan\u0131 ve \u00fcst katman timeout’lar\u0131yla uyumlu olmal\u0131d\u0131r.<\/p>\n

    \u0130\u015f tak\u0131lm\u0131\u015fsa, ayn\u0131 yan etkiyi tekrarl\u0131yorsa, uzun kilit tutuyorsa veya belle\u011fi s\u00fcrekli b\u00fcy\u00fcyorsa s\u00fcreyi art\u0131rmak do\u011fru \u00e7\u00f6z\u00fcm de\u011fildir. Yava\u015f sorgu, d\u0131\u015f servis, dosya I\/O’su veya kod d\u00f6ng\u00fcs\u00fc \u00f6nce d\u00fczeltilmelidir.<\/p>\n

    Yeni ba\u015flayanlar i\u00e7in tan\u0131 ad\u0131mlar\u0131<\/h2>\n
      \n
    1. Kritik hata mesaj\u0131n\u0131, i\u015flemi, tamamlanan kay\u0131t say\u0131s\u0131n\u0131 ve ge\u00e7en s\u00fcreyi kaydedin.<\/li>\n
    2. Hatan\u0131n \u00f6n y\u00fcz, wp-admin, AJAX\/REST, cron, worker veya WP-CLI ba\u011flam\u0131nda olu\u015ftu\u011funu belirleyin.<\/li>\n
    3. Etkin max_execution_time<\/code> de\u011ferini ve proxy\/web sunucusu timeout’lar\u0131n\u0131 kontrol edin.<\/li>\n
    4. \u0130\u015fin parti, devam noktas\u0131, arka plan veya komut sat\u0131r\u0131 se\u00e7ene\u011fi olup olmad\u0131\u011f\u0131n\u0131 inceleyin.<\/li>\n
    5. S\u00fcreyi art\u0131rmadan \u00f6nce yava\u015f sorgu, d\u0131\u015f API, dosya i\u015flemi ve bellek kullan\u0131m\u0131n\u0131 g\u00f6zleyin.<\/li>\n
    6. Tek kontroll\u00fc partiyle tamamlanan birimi, s\u00fcreyi ve kesintiden sonra devam\u0131 do\u011frulay\u0131n.<\/li>\n<\/ol>\n

      \u0130leri teknik yakla\u015f\u0131m<\/h2>\n

      Her parti i\u00e7in i\u015flenen sat\u0131r say\u0131s\u0131, ge\u00e7en s\u00fcre, tepe bellek, sorgu s\u00fcresi ve d\u0131\u015f \u00e7a\u011fr\u0131 say\u0131s\u0131yla ilerleme profili \u00e7\u0131kar\u0131n. \u0130\u015fi bilin\u00e7li olarak kesen bir test, i\u015flemin yinelenmeden kald\u0131\u011f\u0131 yerden devam edip edemedi\u011fini g\u00f6sterir.<\/p>\n