{"id":2439,"date":"2026-02-08T16:41:11","date_gmt":"2026-02-08T16:41:11","guid":{"rendered":"https:\/\/ssblog.eu.enginyr.ing\/?p=2439"},"modified":"2026-02-08T16:41:54","modified_gmt":"2026-02-08T16:41:54","slug":"php-fpm-vs-oom-killer-ghidul-definitiv-de-tuning-pentru-vps-uri-cu-trafic-mare","status":"publish","type":"post","link":"https:\/\/www.serverspan.ro\/blog\/php-fpm-vs-oom-killer-ghidul-definitiv-de-tuning-pentru-vps-uri-cu-trafic-mare\/","title":{"rendered":"PHP-FPM vs. OOM Killer: Ghidul definitiv de tuning pentru VPS-uri cu trafic mare"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Dac\u0103 administrezi un <strong>Linux VPS<\/strong> de suficient timp, \u0219tii procedura: <a href=\"https:\/\/www.serverspan.ro\/blog\/realitatea-tichetelor-de-tip-serverul-meu-merge-greu\/\">site-ul pic\u0103<\/a>, Nginx returneaz\u0103 un &#8220;502 Bad Gateway&#8221;, iar log-urile sistemului (`dmesg` sau `\/var\/log\/syslog`) url\u0103 <code>Out of memory: Kill process (php-fpm)<\/code>. Acesta este OOM (Out of Memory) Killer-ul din kernel-ul Linux \u00een ac\u021biune. Nu este un bug; este un medic de triaj. C\u00e2nd serverul r\u0103m\u00e2ne f\u0103r\u0103 RAM fizic \u0219i Swap, kernel-ul sacrific\u0103 procesul care consum\u0103 cele mai multe resurse pentru a salva sistemul de operare de un &#8220;kernel panic&#8221;.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">La ServerSpan, vedem acest tipar zilnic. Clien\u021bii fac upgrade la <a href=\"https:\/\/www.serverspan.ro\/blog\/ce-este-un-server-virtual-un-ghid-despre-tipurile-de-virtualizare\/\">RAM-ul VPS<\/a> crez\u00e2nd c\u0103 va rezolva problema, doar pentru ca site-ul s\u0103 se pr\u0103bu\u0219easc\u0103 din nou o or\u0103 mai t\u00e2rziu. De ce? Pentru c\u0103 PHP-FPM neconfigurat se comport\u0103 ca un gaz\u2014se extinde pentru a consuma toate resursele disponibile. Acest ghid este o analiz\u0103 \u00een profunzime a gestion\u0103rii ciclului de via\u021b\u0103 al proceselor, care men\u021bine serverele cu trafic mare stabile.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Cauza r\u0103d\u0103cin\u0103: Varia\u021bia dimensiunii proceselor<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Teoria:<\/strong><br>Majoritatea tutorialelor \u00ee\u021bi spun s\u0103 presupui c\u0103 un proces PHP folose\u0219te 30MB sau 50MB. Aceasta este o ghiceal\u0103 periculoas\u0103. Un proces care serve\u0219te o pagin\u0103 static\u0103 din cache poate folosi 20MB. Un proces care gestioneaz\u0103 un checkout WooCommerce cu 40 de plugin-uri active, gener\u00e2nd o factur\u0103 PDF \u0219i trimi\u021b\u00e2nd apeluri API, se poate umfla la 150MB sau 256MB. Dac\u0103 reglezi `max_children` baz\u00e2ndu-te pe media de 20MB, OOM Killer te va vizita de Black Friday.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Implementarea:<\/strong><br>Nu ghici. M\u0103soar\u0103 consumul <em>real<\/em> de memorie al aplica\u021biei tale specifice sub sarcin\u0103. Ruleaz\u0103 aceast\u0103 comand\u0103 pe serverul live pentru a vedea media, minimul \u0219i maximul utiliz\u0103rii memoriei de c\u0103tre procesele PHP-FPM:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>ps -ylC php-fpm --sort:rss | awk '{sum+=$8; ++n} END {print \"Tot=\"sum\/1024\"MB\", \"Avg=\"sum\/n\/1024\"MB\", \"Count=\"n}'<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Folose\u0219te <strong>Media (Avg)<\/strong> din aceast\u0103 comand\u0103 ca punct de referin\u021b\u0103, dar adaug\u0103 o marj\u0103 de siguran\u021b\u0103 de 20% pentru cererile &#8220;grele&#8221;.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2. Matematica supravie\u021buirii: Reglarea <code>pm.max_children<\/code><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Teoria:<\/strong><br>`pm.max_children` este o limit\u0103 dur\u0103 a concuren\u021bei. Dac\u0103 o setezi prea jos, vizitatorii primesc 504 Gateway Timeouts (coad\u0103 de a\u0219teptare). Dac\u0103 o setezi prea sus, vizitatorii primesc 502 Bad Gateways (crash OOM). Scopul este s\u0103 o setezi exact la pragul RAM-ului t\u0103u disponibil.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Formula:<\/strong><br>Trebuie s\u0103 iei \u00een calcul overhead-ul sistemului de operare \u0219i Baza de Date (dac\u0103 e pe acela\u0219i server). <a href=\"https:\/\/www.serverspan.ro\/blog\/mariadb-vs-mysql-8-0-teste-de-performanta-ghid-de-configurare-vps\/\">MariaDB\/MySQL iube\u0219te RAM-ul<\/a>; dac\u0103 nu \u00eel rezervi, PHP \u00eel va &#8220;fura&#8221;, for\u021b\u00e2nd baza de date s\u0103 intre \u00een swap.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Formula Sigur\u0103 ServerSpan:\n# Max_Children = (Total RAM - Rezervat_OS - Rezervat_DB) \/ (Medie_Proces * 1.2)\n\n# Exemplu: VPS de 8GB, MariaDB folose\u0219te 2GB, OS are nevoie de 1GB.\n# Disponibil pentru PHP = 5GB (5120MB)\n# Proces Mediu = 60MB. Buffer = 1.2x (72MB)\n# 5120 \/ 72 = 71 Max Children<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen acest scenariu, setarea `pm.max_children = 71` asigur\u0103 c\u0103, chiar dac\u0103 toate cele 71 de procese sunt active simultan, nu vei pr\u0103bu\u0219i serverul.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">3. Pansamentul pentru &#8220;Memory Leak&#8221;: <code>pm.max_requests<\/code><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Teoria:<\/strong><br>Aplica\u021biile PHP (\u00een special WordPress cu multe plugin-uri) sunt notorii pentru scurgerile de memorie. Un proces worker poate \u00eencepe la 40MB, dar dup\u0103 procesarea a 1.000 de cereri, se poate balona la 120MB din cauza referin\u021belor circulare neeliberate sau a acumul\u0103rii de variabile statice. Setarea implicit\u0103 \u00een multe config-uri este `pm.max_requests = 0` (nu reporni niciodat\u0103). Asta garanteaz\u0103 o moarte lent\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Implementarea:<\/strong><br>For\u021beaz\u0103 reciclarea proceselor. Asta ac\u021bioneaz\u0103 ca un &#8220;garbage collector&#8221; pentru managerul de procese.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># \u00cen \/etc\/php\/8.x\/fpm\/pool.d\/www.conf\npm.max_requests = 500<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Asta \u00eei spune procesului master: &#8220;Dup\u0103 ce un worker a servit 500 de cereri, omoar\u0103-l \u0219i genereaz\u0103 unul proasp\u0103t.&#8221; Overhead-ul CPU pentru regenerare este neglijabil comparativ cu c\u00e2\u0219tigurile de stabilitate prin eliberarea RAM-ului pierdut.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">4. Moduri de gestionare a proceselor: Static vs. Dynamic vs. OnDemand<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Teoria:<\/strong><br>Alegerea managerului de procese (`pm`) corect este critic\u0103 pentru tipul t\u0103u de sarcin\u0103.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Dynamic (Implicit):<\/strong> Men\u021bine un grup de workeri inactivi &#8220;pentru orice eventualitate&#8221;. Bun pentru trafic constant, dar risipitor. \u021aine RAM-ul ocupat chiar \u0219i c\u00e2nd nimeni nu viziteaz\u0103 site-ul.<\/li>\n\n\n\n<li><strong>OnDemand:<\/strong> Genereaz\u0103 procese <em>doar<\/em> c\u00e2nd apare o cerere. Zero consum RAM \u00een repaus. Adaug\u0103 c\u00e2teva milisecunde de laten\u021b\u0103 la prima cerere, dar este esen\u021bial pentru <strong>management VPS<\/strong> al <a href=\"https:\/\/www.serverspan.ro\/blog\/gazduire-vps-pentru-aplicatii-multi-tenant-apache-virtual-hosts-vs-nginx-server-blocks\/\">serverelor multi-tenant<\/a> (ex: g\u0103zduirea a 50 de site-uri mici).<\/li>\n\n\n\n<li><strong>Static:<\/strong> Mi\u0219carea &#8220;Pro&#8221;. Genereaz\u0103 `max_children` imediat \u0219i \u00eei \u021bine \u00een via\u021b\u0103. Zero overhead de generare. Asta ofer\u0103 cea mai bun\u0103 <strong>performan\u021b\u0103 VPS<\/strong> (laten\u021b\u0103 minim\u0103) dac\u0103 ai RAM-ul necesar pentru a o sus\u021bine.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Implementarea:<\/strong><br>Pentru un site dedicat cu trafic mare, treci pe `static`. Elimini acel &#8220;thrashing&#8221; al CPU-ului cauzat de generarea\/uciderea constant\u0103 a copiilor pentru a \u021bine pasul cu v\u00e2rfurile de trafic.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Configura\u021bie de \u00cenalt\u0103 Performan\u021b\u0103 (8GB RAM Dedicat)\npm = static\npm.max_children = 70\npm.max_requests = 1000<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">5. Fr\u00e2na de urgen\u021b\u0103: <code>process_control_timeout<\/code><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Teoria:<\/strong><br>Uneori, un proces PHP \u00eenghea\u021b\u0103. Poate a\u0219teapt\u0103 un apel API curl c\u0103tre o ter\u021b\u0103 parte care s-a blocat, sau a intrat \u00eentr-o bucl\u0103 infinit\u0103. Chiar dac\u0103 Nginx d\u0103 timeout conexiunii c\u0103tre client, procesul PHP continu\u0103 s\u0103 ruleze \u00een fundal, \u021bin\u00e2nd RAM-ul ocupat.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Implementarea:<\/strong><br>Configureaz\u0103 `request_terminate_timeout` \u00een pool-ul t\u0103u PHP-FPM. Acesta este butonul de &#8220;hard kill&#8221;.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Omoar\u0103 orice script care ruleaz\u0103 mai mult de 60s\nrequest_terminate_timeout = 60s<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Combinat cu `pm.status_path`, po\u021bi monitoriza ace\u0219ti zombi. Dac\u0103 vezi procese blocate \u00een starea &#8220;Writing&#8221; pentru 60+ secunde, ai o problem\u0103 de cod, nu una de server.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-css-opacity\"\/>\n\n\n\n<div class=\"wp-block-group has-light-gray-background-color has-background\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n<h3 class=\"wp-block-heading\">[SCENARIU REAL] Furtuna de Cron-uri de la 9:00 AM<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Context Client:<\/strong> O agen\u021bie digital\u0103 g\u0103zduind 30 de site-uri WordPress pe un singur VPS de 16GB.<br><strong>Problem\u0103 Raportat\u0103:<\/strong> &#8220;Serverul \u00eenghea\u021b\u0103 \u00een fiecare zi la 9:00 AM fix. Am f\u0103cut upgrade la CPU, dar nu a ajutat.&#8221;<br><strong>Diagnostic Tehnic:<\/strong> Foloseau configurarea implicit\u0103 `pm = dynamic`. La 9:00 AM, task-urile programate `wp-cron.php` pentru toate cele 30 de site-uri se declan\u0219au simultan. PHP-FPM \u00eencerca s\u0103 genereze copii dinamici pentru 30 de site-uri deodat\u0103. Utilizarea RAM a s\u0103rit de la 4GB la 18GB \u00een 3 secunde. OOM killer a terminat MariaDB pentru a salva kernel-ul.<br><strong>Solu\u021bie Aplicat\u0103:<\/strong> Am trecut toate site-urile pe `pm = ondemand`. Asta a asigurat c\u0103 site-urile inactive foloseau zero RAM. De asemenea, am decalat orarele cron folosind cron-ul de sistem \u00een loc de WP-Cron, e\u0219alon\u00e2ndu-le la minut. V\u00e2rful de memorie a disp\u0103rut complet.<\/p>\n<\/div><\/div>\n\n\n\n<hr class=\"wp-block-separator has-css-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">G\u00e2nduri de final din partea echipei de Ops<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">OOM Killer este un simptom, nu boala. Boala este configurarea gre\u0219it\u0103. Linux presupune c\u0103 \u0219tii ce faci; \u00ee\u021bi d\u0103 sfoara s\u0103 te sp\u00e2nzuri singur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Nu te teme de Swap. \u00centr-un mediu <strong>Cloud VPS<\/strong>, aloc\u0103m \u00eentotdeauna 2-4GB de fi\u0219ier Swap. Da, swap-ul este lent, dar un site lent este infinit mai bun dec\u00e2t un site picat. Swap-ul \u00ee\u021bi cump\u0103r\u0103 cele 30 de secunde de care ai nevoie pentru ca v\u00e2rful de trafic s\u0103 treac\u0103 sau pentru ca OOM killer s\u0103 ia o decizie mai inteligent\u0103. Dac\u0103 atingi constant swap-ul, nu mai face tuning\u2014f\u0103 <a href=\"https:\/\/www.serverspan.ro\/blog\/migrare-de-la-shared-hosting-la-vps-ghidul-zero-downtime-pas-cu-pas\/\">upgrade la plan<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Dac\u0103 administrezi un Linux VPS de suficient timp, \u0219tii procedura: site-ul pic\u0103, Nginx returneaz\u0103 un &#8220;502 Bad Gateway&#8221;, iar log-urile sistemului (`dmesg` sau `\/var\/log\/syslog`) url\u0103 Out of memory: Kill process (php-fpm). Acesta este OOM (Out of Memory) Killer-ul din kernel-ul Linux \u00een ac\u021biune. Nu este un bug; este un medic de triaj. C\u00e2nd serverul r\u0103m\u00e2ne [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2436,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[773,13949,9010,13954,732,5885,1154,13957,13958,13946,5980,6149,10147,13951,591,13953,13959,3703,590,738,13955,6011,13939,13948,13952,13966,13947,4550,3884,13950,13960,13962,13961,13964,13963,5985,13956,10654,13965,2216],"class_list":["post-2439","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials","tag-backup-vps","tag-cel-mai-bun-vps-hosting","tag-cloud-vps","tag-comenzi-linux-vps","tag-configurare-vps","tag-depanare-vps","tag-gazduire-cloud","tag-latenta-vps","tag-latime-de-banda-vps","tag-managed-cloud-vps","tag-managed-vps","tag-migrare-vps","tag-monitorizare-vps","tag-panou-de-control-vps","tag-performanta-vps","tag-preturi-vps","tag-recenzii-vps","tag-secure-vps-hosting","tag-securitate-vps","tag-server-privat-virtual","tag-server-vps","tag-stocare-vps","tag-vps-cpu","tag-vps-de-inalta-performanta-3","tag-vps-dedicat","tag-vps-gratuit","tag-vps-ieftin","tag-vps-linux","tag-vps-management","tag-vps-nvme","tag-vps-pentru-business","tag-vps-pentru-developeri","tag-vps-pentru-gaming","tag-vps-pentru-trading","tag-vps-pentru-website","tag-vps-ram","tag-vps-self-hosted","tag-vps-vs-cloud","tag-vps-vs-dedicat","tag-vps-windows"],"_links":{"self":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2439","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2439"}],"version-history":[{"count":2,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2439\/revisions"}],"predecessor-version":[{"id":2441,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2439\/revisions\/2441"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/2436"}],"wp:attachment":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2439"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2439"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2439"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}