The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers Linux VPS plans with full root access, unlimited traffic on a 1 Gbps port and a 14-day free trial.
The reliable way to optimize Nginx and PHP-FPM is to measure your workload, give each materially different site an appropriate pool, size pm.max_children from real worker memory, and verify that Nginx reaches the intended local listener. Use a Unix socket for a single-host VPS, protect status and slow logs, and add FastCGI caching only for responses that are genuinely safe to cache. There is no universal worker count: the correct value depends on available RAM, measured PHP worker size, CPU, database load, and request duration.
What Nginx and PHP-FPM are doing
Nginx handles the client connection, TLS, static files, buffering, and access logging. For a PHP request it passes FastCGI parameters to PHP-FPM, which runs the script and returns the response. In Nginx, the ngx_http_fastcgi_module supplies fastcgi_pass, parameter forwarding, response buffering, and FastCGI-cache controls.
Most performance failures occur at the boundary between the two services rather than in a single directive. Nginx can point at a socket that does not exist, use a different PHP version from the running pool, or calculate the wrong script path. PHP-FPM can have too few workers, consume all memory, or spend most of its time waiting on a database. Optimization therefore starts with a correct, observable configuration and proceeds in measured changes.
Inventory the VPS before changing a pool
Record the resources and services that compete with PHP. The inventory is the baseline against which every later change is judged.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
- Total RAM and CPU cores, including whether the VPS uses burstable CPU credits.
- Ubuntu release and installed PHP-FPM version. Ubuntu commonly installs versioned services such as
php8.3-fpm; use the version actually installed on your host. - Every enabled site, its traffic pattern, and whether it is mostly anonymous pages, authenticated sessions, an API, a queue worker, or administration.
- Database engine and its resident memory, storage type, and largest tables or queries.
- Existing pool files in
/etc/php/<version>/fpm/pool.d/, Nginx server blocks, and current error, access, FPM slow, and system logs.
Do not size PHP from total RAM. Reserve memory for Ubuntu, Nginx, the database, monitoring agents, filesystem cache, and a safety margin for bursts. A configuration that works only while swap is active is not optimized.
Make the Nginx-to-FPM connection unambiguous
Check the active listener
Each FPM pool has a listen value. It may be a Unix socket such as /run/php/php8.3-fpm-site.sock or a TCP address such as 127.0.0.1:9071. Confirm the running service has created that listener before editing Nginx. A socket path in Nginx must match the pool character-for-character.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11sudo systemctl status php8.3-fpm
sudo ss -lx | grep /run/php
sudo ss -ltnp | grep 9071Use the service name and paths for your installed PHP version. If the service is stopped, fix its configuration and start it before diagnosing Nginx.
Use an explicit PHP location
A minimal server block location looks like this. The exact include files differ between Ubuntu releases, so keep the directives that are present in your installation and verify the result with nginx -t.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
location ~ .php$ {
try_files $uri =404;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
fastcgi_pass unix:/run/php/php8.3-fpm-site.sock;
}try_files prevents Nginx from sending a nonexistent path to PHP. SCRIPT_FILENAME must resolve to the real file; an incorrect value commonly produces a blank response, a 404, or a security mistake in which unintended files are interpreted. If your distribution supplies /etc/nginx/snippets/fastcgi-php.conf, inspect it rather than blindly duplicating its parameters.
Validate in the right order
- Run
sudo nginx -t. Correct syntax and missing-file errors before reloading. - Run
sudo systemctl reload nginxso existing connections are not needlessly dropped. - After changing pool definitions or PHP-FPM settings, run
sudo systemctl restart php8.3-fpm(or the installed version), then check its status and journal. - Request a harmless PHP health endpoint and inspect both the HTTP status and the Nginx and FPM logs.
Decide whether separate pools are worthwhile
A pool can have its own Unix user and group, listener, PHP settings, logs, and process limits. Give a site its own pool when it needs a different Unix identity, independent restart behavior, a separate concurrency ceiling, or distinct observability. A small static-content site and a high-traffic application often benefit from different limits.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Do not create a pool for every virtual host by habit. Every pool adds configuration, idle-process decisions, logs, and another limit to maintain. On a small VPS, several pools can collectively reserve more memory than one shared pool, while a busy site can still starve others unless limits are deliberately set.
Pools are operational boundaries, not complete security boundaries. The PHP manual states: “Pools are not a security mechanism, because they do not provide full separation; e.g. all pools would use a single OPcache instance.” Continue to isolate files, credentials, and system privileges with normal operating-system controls.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Pool comparison
| Design | Advantages | Costs and risks | Use when |
|---|---|---|---|
| One shared pool | Lowest configuration overhead and efficient sharing of workers | Sites share a user, limits, logs, and restart impact | Sites have similar trust, traffic, and PHP requirements |
| Pool per site | Independent user, listener, limits, logs, and restart behavior | More idle memory and more tuning points; not a full security boundary | Sites need different permissions, reliability or concurrency policies |
| Pool per workload | Separates web requests from a special API or long-running workload | Requires careful capacity budgeting so one workload cannot consume all RAM | Request duration or resource profile differs materially |
Size pm.max_children from measurements
pm.max_children is the concurrency ceiling for a pool. PHP documents it as the limit on the number of simultaneous requests that will be served. It is not a target throughput number and it does not make a slow database query faster.
The sizing method
- Measure or estimate the pool’s worker resident memory under representative traffic. Use a busy period, not an idle process, and record several samples. The 95th-percentile worker size is safer than a single unusually small sample.
- Calculate memory available to this pool: total RAM minus Ubuntu and Nginx usage, database and cache usage, monitoring, other pools, and a safety reserve for bursts and filesystem cache.
- Divide available pool memory by the measured worker size and round down. This is a starting ceiling, not a promise that the VPS can sustain that many expensive requests.
- Load-test or observe production traffic, then check swap activity, memory pressure, CPU saturation, request latency, and FPM queue indicators. Lower the ceiling if the system becomes memory-bound; raise it only when workers are queued while memory and CPU remain healthy.
For example, if 1,200 MB is deliberately available to a pool and a representative worker uses 80 MB resident, the arithmetic starting point is 15 workers. The figures are illustrative; substitute your measurements and keep headroom for variation. Copying pm.max_children = 50 from another VPS is meaningless when its PHP extensions, code paths, database, and RAM differ.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsRecognize the trade-off
- Too low: requests queue behind FPM, producing rising latency even though RAM is comfortable.
- Too high: concurrent PHP work, database connections, and per-worker memory can exhaust RAM, invoke the OOM killer, and make every service slower.
- High worker counts do not help CPU-bound code once all cores are busy; they may increase context switching and database contention.
- Long-running requests occupy a worker for their entire duration, so a few slow endpoints can consume the ceiling. Find and fix the slow dependency instead of only adding workers.
Choose static, dynamic, or ondemand
PHP-FPM documents three process-management modes. The right choice depends on steady-state traffic, burstiness, idle-memory tolerance, and request duration.
| Mode | How workers are created | Strengths | Trade-offs |
|---|---|---|---|
static |
Exactly pm.max_children workers remain configured |
Predictable capacity and no worker creation during a burst | Highest idle memory use; unsuitable when the fixed count does not fit the VPS |
dynamic |
Starts at pm.start_servers, keeps at least pm.min_spare_servers, and trims above pm.max_spare_servers, never exceeding pm.max_children |
Good general-purpose balance between warm capacity and idle memory | More tuning parameters and some process churn during changing demand |
ondemand |
Starts workers only when requests arrive and retires idle workers after the configured idle timeout | Low idle memory for quiet or intermittent sites | Cold-start latency during bursts and less predictable first-request response |
Use dynamic as a practical starting point for a continuously used application, provided its spare-process settings fit the memory budget. Use ondemand for low-volume sites where conserving RAM matters more than eliminating cold starts. Use static only when traffic is steady and the fixed worker footprint is comfortably affordable.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Example pool files
Pool files are normally stored under the versioned FPM directory. The following examples show the important relationships; choose values from measurement rather than copying them.
[app]
user = app
Group = app
listen = /run/php/php8.3-fpm-app.sock
listen.owner = www-data
listen.group = www-data
listen.mode = 0660
pm = dynamic
pm.max_children = 15
pm.start_servers = 3
pm.min_spare_servers = 2
pm.max_spare_servers = 5
pm.max_requests = 500
access.log = /var/log/php8.3-fpm-app.access.log
slowlog = /var/log/php8.3-fpm-app.slow.log
request_slowlog_timeout = 5sThe capitalized group directive should be written exactly as accepted by your PHP version; most installations use lowercase group. The pm.max_requests recycle limit can reduce the impact of gradual leaks, but recycling too aggressively adds process-start overhead. A slow log timeout should reflect your application’s normal response-time distribution, not an arbitrary value.
Prefer a Unix socket on a single-host VPS
A Unix socket keeps FastCGI on the local machine and avoids exposing a TCP listener. Set ownership and mode so Nginx’s user can connect while unrelated users cannot. In the example above, the socket is owned by www-data and mode 0660; verify that your pool user, Nginx group, and distribution defaults match.
Use TCP only when a separate host, container, namespace, or other architectural requirement makes it necessary. Bind it to a specific local address rather than all interfaces. If the design requires TCP, configure PHP-FPM’s listen.allowed_clients with the exact trusted address list. PHP warns that an exposed FastCGI endpoint can permit arbitrary code execution, so never publish an unauthenticated FPM port to the Internet.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Socket failure symptoms
- 502 Bad Gateway: the service is stopped, the socket path is wrong, permissions deny Nginx, or no worker can accept the request.
- Permission denied in the Nginx error log: inspect socket owner, group, mode, and the account running Nginx.
- Connection refused on TCP: the pool is not listening on that address or a local firewall policy blocks it.
- Requests execute the wrong code: check
SCRIPT_FILENAME, document root, and which PHP version owns the listener.
Use buffering and caching for different purposes
FastCGI buffering
Buffering controls how Nginx reads and stores an upstream response. It can prevent a slow client from tying up the upstream connection and smooth responses that arrive in chunks. Tune buffer sizes only after observing response sizes and Nginx warnings; oversized buffers multiply memory use across concurrent requests. Buffering does not reduce PHP execution time and does not make a response cacheable.
FastCGI cache
Caching can avoid running PHP for repeatable responses, but correctness rules come first. Define the cache key, methods, validity periods, and bypass conditions explicitly. Typical bypass conditions include logged-in or session cookies, an Authorization header, administrator paths, shopping-cart or checkout routes, preview parameters, and any state-changing method such as POST.
A safe pattern is to cache only anonymous GET and HEAD responses whose output is identical for all eligible visitors, then bypass and do not store personalized or state-changing responses. Test cache headers and purge behavior after publishing content. A cache hit can hide PHP saturation in the short term, while a misclassified response can leak one user’s data to another, so treat caching as a separate design decision from pool tuning.
Expose observability without exposing internals
Enable an FPM status endpoint and a slow-request log for each important pool, but publish them only through a protected internal location or an allowlisted administration network. The status view helps distinguish a full worker queue from a quiet pool; the slow log identifies scripts and call paths that hold workers.
Correlate several signals:
- Nginx access-log latency and upstream status codes.
- FPM active, idle, and maximum-active process counts, plus listen-queue pressure where available.
- Per-process RSS, total memory, swap activity, CPU utilization, and load.
- Database connection counts, lock or query latency, disk I/O, and network delays.
When latency rises, first determine whether PHP workers are saturated or merely waiting on a database, filesystem, external API, or network. Increasing pm.max_children cannot repair a downstream bottleneck and may amplify it.
Quick Recap
A controlled tuning workflow
- Capture a baseline during representative traffic: latency percentiles, error rate, worker counts, memory, CPU, swap, and database metrics.
- Correct wiring and permissions, then verify a real PHP request reaches the intended pool.
- Choose pool boundaries based on users, limits, and workload differences, not on the number of virtual hosts alone.
- Set a conservative
pm.max_childrenfrom measured worker memory and reserved RAM. - Choose a process mode. Start with
dynamicfor sustained traffic orondemandfor intermittent traffic; usestaticonly with a known fixed footprint. - Change one setting at a time. Test configuration, reload Nginx, restart FPM only when its configuration changed, and record the exact change.
- Observe long enough to include a normal peak and a quiet period. Compare the same latency, memory, queue, and error metrics with the baseline.
- Investigate slow requests and database behavior before raising concurrency. Add FastCGI caching only after defining and testing bypass rules.
Common mistakes and recovery
| Symptom | Likely cause | Recovery |
|---|---|---|
| All PHP requests return 502 | Wrong listener, stopped FPM, or socket permission problem | Check systemctl status, listener existence, Nginx error log, and socket ownership; restore the last known-good listener and reload. |
| VPS becomes unresponsive after raising workers | Aggregate worker and database memory exceeded RAM | Lower pool ceilings, stop runaway processes if necessary, disable swap-dependent settings, and recalculate from measured RSS with larger headroom. |
| First request after idle is slow | ondemand worker startup or application bootstrap |
Use dynamic with a small warm reserve if memory permits, or optimize startup work. |
| One site degrades every other site | Shared pool or unbounded concurrency | Separate the workload when justified and assign explicit per-pool ceilings; also check shared database and disk bottlenecks. |
| Private or cart pages appear cached | FastCGI cache bypass rules are incomplete | Disable cache for the affected routes, purge existing objects, and add cookie, authorization, method, and path exclusions before re-enabling. |
Practical decision checklist
- Is the Nginx
fastcgi_passtarget the listener created by the intended FPM pool? - Does
SCRIPT_FILENAMEmap to a real file under the site root? - Can the Nginx account access the Unix socket, and is any TCP listener local and allowlisted?
- Have you reserved RAM for Ubuntu, Nginx, databases, other pools, monitoring, and bursts?
- Is
pm.max_childrenbased on measured worker RSS rather than a copied number? - Does the selected process mode match steady-state traffic and idle-memory limits?
- Are status and slow logs protected, and are latency, queue, memory, CPU, and database metrics being compared after each change?
- Are cache keys and bypass rules proven safe for anonymous, cacheable responses only?
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
