Tune PHP-FPM Pools in WHM Before Your Traffic Spikes
Find Max Children, Max Requests and Process Idle Timeout in WHM, measure what each PHP worker costs in memory, and raise limits without crashing your server.
The short answer
Open WHM Home > Software > MultiPHP Manager, go to User Domain Settings, and open PHP-FPM Settings for the domain to change Max Children, Max Requests and Process Idle Timeout. cPanel's defaults are 5, 20 and 10 seconds. Before raising Max Children, measure how much memory one PHP worker uses and make sure the server has room for every extra worker.

Reading options
On this page
- What PHP-FPM pools actually are
- Before you start
- Step 1: Check whether PHP-FPM is on
- Step 2: Enable PHP-FPM for a test domain
- Step 3: Find the PHP-FPM Pool options
- Step 4: Understand each setting before you change it
- Step 5: Measure memory per PHP process
- Step 6: Change the values
- Step 7: Roll back if needed
- Variants that change the steps
- How to check it worked
- Troubleshooting
- Pro tips and security notes
- The one message worth forwarding
- Reader questions
- Sources & further reading
Before you start
WHM and root or authorised SSH access; the correct cPanel account username; a staging or test site; recent backups; permission to monitor and change the server; a rollback window.
You change PHP-FPM pool settings per domain in WHM Home > Software > MultiPHP Manager, on the User Domain Settings tab. Each domain with PHP-FPM turned on has its own Max Children, Max Requests and Process Idle Timeout values, and you can raise or lower them there. The trick is to size them from real memory measurements, because a number picked by feel can take the whole server down.
Here is the fact that surprises most people. cPanel's documented default for Max Children is 5, which means a busy shop gets at most five PHP processes working at the same moment, no matter how many visitors are waiting.
By the end of this guide you will know how to check whether a domain uses PHP-FPM, change its pool values safely, measure what each PHP process costs in memory, and roll back if something goes wrong.
What PHP-FPM pools actually are
PHP-FPM stands for FastCGI Process Manager. In plain words, it is a program that keeps a group of PHP processes ready, so your web server can hand them PHP work instead of starting PHP from scratch for every request. cPanel describes it as "an alternative PHP module that allows a website to handle more requests than it normally could."
A pool is one of those groups of processes. A worker (PHP's manual calls it a child process) is a single process inside the pool that handles one request at a time.
Think of a small restaurant kitchen. The pool is the kitchen, and each worker is a cook. Max Children is the number of cooks you allow in the kitchen at once. Max Requests is how many orders a cook handles before you send them home and bring in a fresh one. Process Idle Timeout is how long a cook can stand around with nothing to do before they are sent home.
More cooks serve more orders, but each one takes up space. Memory is your kitchen space.
Before you start
- Root access to WHM, or a reseller account with access to MultiPHP Manager. Your hosting provider can switch this interface off for resellers, so if you cannot see it, ask them.
- The domain's PHP version set to a real version, such as PHP 8.2, and not to inherit. cPanel will not let you enable or edit PHP-FPM on a domain set to inherit.
- A written record of the current values for the domain you plan to change. A screenshot works too.
- SSH or WHM Terminal access, so you can measure memory with a command.
- A quiet time window, when traffic is low and you can watch the site for at least 30 minutes after the change.
- Risk level: medium. A bad value will not delete data, but it can make a site slow or push the whole server into memory trouble.
Quick tip: learn the screens on a small test site you own before you touch a busy store.
Step 1: Check whether PHP-FPM is on
Open the User Domain Settings tab
Log in to WHM and go to WHM Home > Software > MultiPHP Manager. Click the User Domain Settings tab.
You should see a list of domains, each with its PHP version and a PHP-FPM toggle showing Enabled or Disabled.
If the column says Unavailable, the domain is set to inherit its PHP version. Step 2 fixes that.
Step 2: Enable PHP-FPM for a test domain
Clear inherit if it is set
Still in WHM Home > Software > MultiPHP Manager > User Domain Settings, find the PHP Version column for your test domain. If the Inherit box is ticked, untick it, choose a specific PHP version, and click Apply.
Afterwards, the PHP-FPM toggle for that domain becomes available.
Heads up: if other domains inherit their PHP version from this one, changing the parent's version changes theirs too. Check who inherits before you apply.
Turn the toggle on
Set the PHP-FPM toggle for the domain to Enabled.
You should see the status change to Enabled, and a PHP-FPM Settings option will now appear for that domain.
Know the shared document root rule
A document root is the folder a domain's website files live in. cPanel's documentation says that when you enable PHP-FPM on a domain that shares a document root, "the system applies the change to all domains that use that document root." Refresh the page afterwards to see the updated status on the related domains.
Step 3: Find the PHP-FPM Pool options
Open the domain's PHP-FPM Settings
On the User Domain Settings tab, open PHP-FPM Settings for your test domain. You will only see this option while PHP-FPM is Enabled for that domain.
Scroll to the section called PHP-FPM Pool options. You should see three fields: Max Requests, Max Children and Process Idle Timeout.
Write down what is there now
Copy the current values into a note first. At the time of writing (20 November 2026), cPanel documents these defaults and allowed ranges:
- Max Children: default 5, allowed 1 to 10000.
- Max Requests: default 20, allowed 1 to 10000000.
- Process Idle Timeout: default 10 seconds, allowed 1 to 10000000.
cPanel says you must enter a whole number inside each range.
Step 4: Understand each setting before you change it
Max Children
cPanel's definition is short: "The maximum number of PHP-FPM processes the server will spawn." PHP's own manual adds that this option "sets the limit on the number of simultaneous requests that will be served."
So if Max Children is 5 and a sixth visitor needs PHP at the same moment, that visitor waits. Each extra worker uses its own memory, so this is the setting that can run a server out of RAM.
Max Requests
cPanel defines it as "The maximum number of requests a process can serve before it spawns a new process."
PHP's manual explains why this exists: it "can be useful to work around memory leaks in 3rd party libraries." A memory leak is when a program keeps grabbing memory and never gives it back. Restarting workers now and then clears that slow build-up.
PHP's own default for this is 0, meaning a worker never restarts. cPanel's default of 20 recycles workers far more often.
Process Idle Timeout
cPanel defines it as "The amount of time, in seconds, that a process can be idle before the system kills it." Idle means the worker is alive but has no request to handle.
Heads up: PHP's manual says the matching setting, pm.process_idle_timeout, is "Used only when pm is set to ondemand." The pm setting is the mode the process manager uses to decide how many workers to keep running. cPanel's page does not say which mode its pools use, so if changing this value seems to have no effect, that may be why.
Step 5: Measure memory per PHP process
This is the step most people skip, and it is the one that tells you how high Max Children can go.
Take a "before" memory reading
Open an SSH session as root, or the Terminal in WHM, and run this command to see the server's overall memory in mebibytes.
free -mYou should see rows for Mem and Swap. Note the number in the available column, which the free manual describes as an "estimation of how much memory is available for starting new applications, without swapping."
List the PHP-FPM workers and their memory
Next, load a few representative pages on a staging or test copy so some workers are busy. Then identify the cPanel account that owns the domain in WHM and replace the placeholder below. These are unexecuted examples for an authorised server administrator.
CPUSER='replace_with_cpanel_account'
ps -f -U "$CPUSER" | grep '[p]hp-fpm'cPanel documents this account-scoped command for reviewing PHP-FPM workers. It avoids mixing the target account with the master process and unrelated pools. To see resident memory (RSS) for the same account, use:
ps -U "$CPUSER" -o pid=,rss=,args= --sort=-rss | grep '[p]hp-fpm'RSS is shown in KiB. Divide by 1024 for an approximate MiB value. Sample several representative requests and record the larger worker readings. RSS includes shared pages, so it is a conservative planning signal rather than exact per-worker private memory. Confirm that the command output belongs to the intended account before using it in capacity calculations.
Why this matters: a server-wide process list can make one domain look more expensive than it is, or hide that another account owns the largest workers.
A cautious sizing method (author-proposed)
The calculation below is an author-proposed planning method, not a cPanel formula and not a benchmark from this article. Measure under representative load, then watch CPU, memory and I/O after every change, as cPanel recommends.
First, decide how much memory you are willing to give PHP on this server, after the database, mail and the operating system have what they need. Then take the largest worker size you saw during busy page loads. Divide the first number by the second, and you have a rough ceiling for the total number of PHP workers across all the domains on the server.
Made-up example: these numbers are invented to show the arithmetic. Say your server shows 6000 MB available, and you decide PHP can use 3000 MB of it. Your biggest worker during a product page load shows about 100 MB. That gives a ceiling of about 30 workers in total. If you have one busy shop and four quiet sites at the default of 5 each, the quiet sites can use up to 20, which leaves about 10 for the shop.
Heads up: Max Children is set per domain, and every domain with PHP-FPM enabled has its own value. Raising each domain a little can add up to a big number across the server.
Step 6: Change the values
Change one value at a time
Go back to WHM Home > Software > MultiPHP Manager > User Domain Settings, and open PHP-FPM Settings for your test domain.
Author-proposed starting points, not cPanel defaults or guarantees:
- Max Children: raise it in small steps from the default, for example from 5 to 8, and stay under the share you worked out in Step 5.
- Max Requests: leave it at 20 for your first change. Once memory looks steady over a few days, you can try a higher value so workers restart less often.
- Process Idle Timeout: leave it at 10 unless you have a clear reason to change it.
Validate and save
Click Validate Settings to check the values are valid. Then click Update to save them.
Your new values should now show as saved. Before saving, Reset Settings returns the fields to their saved values.
Step 7: Roll back if needed
Rolling back is the same path in reverse. Go to WHM Home > Software > MultiPHP Manager > User Domain Settings, open PHP-FPM Settings for the domain, type the old values from your note, then click Validate Settings and Update.
If the site is badly broken and you need it working right now, you can switch PHP-FPM off for the domain with the toggle on the User Domain Settings tab. For several domains at once, select them and click Disable PHP-FPM.
Heads up: Reset Settings cannot bring back values you already saved. That is why the written note matters.
Variants that change the steps
LiteSpeed Web Server
If your server runs LiteSpeed Web Server instead of Apache, these screens behave differently. cPanel's documentation says: "If an active LiteSpeed Web Server installation exists on your server, you cannot edit these settings." It also says the system sets your PHP handler to lsphp.
Which PHP versions you can pick
At the time of writing (20 November 2026), cPanel's documentation says EasyApache 4 supports PHP 7.4 and PHP 8.1 through 8.5, and that the cPanel default profile includes PHP 8.1 and 8.2. EasyApache 4 is the WHM tool that installs PHP versions and Apache modules.
If a version you want is missing from the dropdown, it is either not installed or not available to that account. A server administrator can install it through EasyApache 4.
Global settings versus one domain
The System Settings tab at WHM Home > Software > MultiPHP Manager holds server-wide PHP-FPM defaults. cPanel says changes there "will apply to all new accounts' PHP-FPM configurations" but "will not change existing accounts' configurations unless you set those accounts to inherit global settings." For a store that already exists, change the domain on the User Domain Settings tab instead.
How to check it worked
A test page load that returns 200
Run this command from your own computer or from the server, replacing example.com with your test domain.
curl -I https://example.com/The -I option fetches only the response headers. The first line should show a 200 status code. Also open a product page or a search in a browser.
Read the PHP-FPM error log
cPanel's support knowledge base says domain PHP-FPM logs live under /opt/cpanel/ea-php*/root/usr/var/log/php-fpm/, one folder per PHP version. Run this command as root to list the log files on your server.
find /opt/cpanel/ea-php*/root/usr/var/log/php-fpm/ -type f -name error.logThen search the log for your domain's PHP version for messages about the worker limit. This example uses the PHP 8.2 folder, so change ea-php82 to match your version.
grep max_children /opt/cpanel/ea-php82/root/usr/var/log/php-fpm/error.logNew max_children lines after your change mean the pool still hits its limit at busy moments.
Compare memory before and after
Run free -m again at a similar traffic level to your "before" reading. Then run the ps command from Step 5 again.
If available memory has dropped sharply and Swap use is climbing, your new value is too high.
Troubleshooting
The Enable PHP-FPM toggle is missing or shows Unavailable
Symptom: on the User Domain Settings tab, the PHP-FPM column says Unavailable, and there is no toggle to switch on.
Cause: the domain's PHP version is set to inherit. cPanel says you "cannot modify a domain's PHP-FPM settings if its PHP version is set to Inherit or if PHP-FPM is not available for its PHP version."
Fix: untick Inherit, choose a specific PHP version and click Apply. If the toggle still does not appear, an administrator can check that version in EasyApache 4.
A "not enough memory" warning when enabling on all domains
Symptom: on the System Settings tab, you try to switch PHP-FPM on everywhere and get a warning instead.
Cause: cPanel checks memory first. Its documentation says that if the system "does not have enough memory to convert all domains to use PHP-FPM," it will not enable PHP-FPM for all domains and shows a warning. The Enable on All Domains option only appears when the server has enough memory.
Fix: enable PHP-FPM only on the domains that need it most, one at a time on the User Domain Settings tab, and measure memory as you go.
Changes to global settings do not reach an existing account
Symptom: you changed the defaults on the System Settings tab, but an existing site still shows the old pool values.
Cause: global changes apply to new accounts only, unless the existing account is set to inherit global settings.
Fix: change that domain directly in WHM Home > Software > MultiPHP Manager > User Domain Settings.
The PHP-FPM fields are locked on a LiteSpeed server
Symptom: you can see the MultiPHP Manager screens, but you cannot edit the PHP-FPM settings.
Cause: an active LiteSpeed Web Server installation blocks editing, and the PHP handler is set to lsphp.
Fix: tune PHP through LiteSpeed's own settings, or ask your host.
The server runs out of memory after you raised Max Children
Symptom: soon after the change, every site on the server gets slow, free -m shows very little available memory, and Swap use keeps climbing.
Cause: too many workers running at once need more RAM than the server has, so it starts swapping, which means using the disk as slow overflow memory.
Fix: lower Max Children back toward your old value using the rollback steps, measure again with ps during a busy period, and try a smaller increase.
PHP-FPM switched off after a domain rename
Symptom: you renamed an account's primary domain, and the site is no longer using PHP-FPM.
Cause: cPanel says that when a primary domain with FPM enabled is renamed, "the system will disable FPM for the new domain."
Fix: a server administrator turns it back on for the new domain name on the User Domain Settings tab, then re-enters the pool values from your note.
A max children warning in the cPanel log, not the domain log
Symptom: you find a warning like server reached max_children setting (25), consider raising it in /usr/local/cpanel/logs/php-fpm/error.log.
Cause: cPanel's support article explains that this log belongs to cPanel's internal PHP-FPM service, which runs things like phpMyAdmin and Webmail. It is separate from the PHP-FPM pools your websites use.
Fix: do not change your domain pools because of this one. Follow cPanel's support article for that internal service instead.
Pro tips and security notes
Change one value at a time, then measure. If you change three things at once and the server struggles, you will not know which one caused it.
Write down the date, domain, old value, new value and memory reading after each change. It makes rollback easy.
A higher Max Children uses more RAM. Past a point it makes the whole server slower, because every site fights over memory. More workers only help while there is memory to spare.
Do your testing in a calm week before a busy sales period, so you have time to watch memory and roll back.
Only give WHM root or reseller access to people who need it, since one careless pool change can slow every site on the server.
On shared hosting you usually cannot reach WHM at all, which is normal. If you want a refresher on the basics first, see our guide on what web hosting is.
The one message worth forwarding
If you do not manage the server yourself, send this to your host or sysadmin:
Hi, before our next busy sales period I would like to review the PHP-FPM pool settings for example.com in WHM (MultiPHP Manager > User Domain Settings). Could you please tell me the current Max Children, Max Requests and Process Idle Timeout values, how much memory one PHP-FPM worker for this site uses during a busy page load, and whether the PHP-FPM error log shows max_children warnings? If there is room in memory, I would like to raise Max Children in small steps, with a before and after memory check each time. Please let me know if the server runs LiteSpeed, since I understand these settings cannot be edited there. Thank you.Measure what one worker costs, then give each pool only as many workers as your memory can actually hold.
Reader questions
Do I need to restart Apache after saving PHP-FPM pool values in WHM?
cPanel's documentation for this screen only describes clicking Update to save, and does not list a separate restart step. Confirm the result with a page load and a memory reading rather than assuming.
Can I edit PHP-FPM pool settings from cPanel instead of WHM?
The pool options are documented in WHM's MultiPHP Manager, and the cPanel MultiPHP Manager page says administrators enable or disable PHP-FPM in WHM. If you only have cPanel access, ask your host.
Can I set Max Children to 0 to mean unlimited?
No. cPanel only accepts whole numbers from 1 to 10000 for Max Children, so there is no unlimited setting.
Is a kibibyte the same as a kilobyte?
Almost. A kibibyte is 1024 bytes and a kilobyte is 1000 bytes, so for sizing PHP workers the difference is small enough to ignore.
Should I turn on PHP-FPM for every domain on the server?
Only if the server has the memory for it. cPanel checks memory before it offers Enable on All Domains, and turning it on only where it is needed keeps the total number of workers lower.
How long should I watch the server after changing a pool value?
As a rule of thumb from experience, watch for at least 30 minutes, then check again during the next busy period. Problems from too many workers usually show up only when traffic is high.
Was this guide helpful?
Help us make the next update better.
Sources & further reading
- cPanel Docs, MultiPHP Manager for WHM, User Domain Settings
- cPanel Docs, MultiPHP Manager for WHM, System Settings
- cPanel Docs, MultiPHP Manager for cPanel
- cPanel Docs, MultiPHP Manager for WHM
- PHP Manual, FPM configuration
- cPanel Support, How to check if a website is reaching max children in PHP-FPM
- cPanel Support, Server reached max children setting in cPanel PHP-FPM
- Linux man page, ps(1)
- Linux man page, free(1)
- curl man page
- cPanel Support, How to review PHP-FPM processes per account
What changed
Scoped PHP-FPM process measurement to the intended cPanel account, clarified RSS limitations, labelled the sizing method as author-proposed and unexecuted, and added original article/social media.
Originally published . About our editorial updates.



