This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
pm.max_children comes from how much memory one worker uses and how much you will give the pool. The calculator uses numbers you type. It does not see the server. php.ini drafts settings. The version checker compares versions you type. None of them reload PHP.
The pool user is not root. Do not change the user to root to fix a permission error. display_errors stays off on a production draft. A version jump is its own ticket.
One pool. Do not apply the file during the reading. 192.0.2.10/24 and example.com are documentation. They stay in the note.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the host named in the ticket. Read the draft, then the host, then decide.
Rollback is the file, the package version, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.
- Type the memory numbers you measured or mark them as guesses.
- Read max_children.
- Draft the pool with a user that is not root.
- Leave display_errors off in a production draft.
- Do not reload during the reading.
- Stop.
Mistakes that outlive the command
Tuning PHP-FPM goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- The pool run as root.
- display_errors on in production.
- Guessed memory treated as a measurement without a label.
- A reload during the reading.
- Two versions installed in one hour.
Decisions to write down
One decision for Tuning PHP-FPM: The user is not root. The numbers are labeled. display_errors is off on a production draft. No reload yet. And one pool.
Checks before you call it done
Confirm this before you call the change done: max_children is written. The user is written. The numbers are labeled measured or guessed. No reload was done. And display_errors is off if the draft is for production. If one of those fails, stop.
# Pool user is not root.
# Numbers you type, labeled.
# Do not reload during the reading.Before you leave the host
Tuning PHP-FPM ends when the hostname in the prompt matches the hostname in the ticket. If it does not, you are on the wrong host. Stop. A command that succeeded on the wrong host is not progress.
The draft stays a draft until a person has read the names in it. A generator does not log into the host and does not know which disk is empty. You delete a line that names a host, a path, or an account you did not write down.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a host because a draft included them.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save in the ticket or in git. The real secret stays in the password store.
One change is the window. If two things move and the result is wrong, you will not know which one did it. The next change waits for its own page.
If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied change produces a host nobody can rebuild. Restore the copy you took first.
A second person reads the hostname and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the host alone.
This page is a planning guide. It is not a vendor manual, not an official standard, and not permission to touch a host you do not administer. You do not disable a firewall, AppArmor, or SELinux to make a check pass.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.