# WHMCS Performance Tuning

> PHP, web server and cron tuning for busy WHMCS installs: handler, limits, slow cron tasks and server resources.

Runtime tuning for busy WHMCS installs: PHP version and pool, memory and time limits, web server workers, slow cron tasks and dead servers, measured before and after.

- **Price:** Starting at $149
- **Billing:** One-time, fixed scope
- **Category:** Server Management
- **Quote turnaround:** Fixed-price quote within 24 hours
- **Start a project:** https://whmcspilot.com/start-project
- **Details:** https://whmcspilot.com/services/whmcs-performance-tuning
- **Last updated:** 2026-11-05

## Overview

WHMCS performance tuning covers the runtime underneath every page: the PHP version and handler, PHP limits, the web server, server resources and the time the system cron takes to finish. It suits busy installs where admin actions hang, the daily cron overruns, or server load climbs at the same hour each day. Tuning one install on one server starts at $149. Heavy themes and scripts in the browser are handled by [speed optimization](/services/whmcs-speed-optimization), and oversized tables or slow queries by [database optimization](/services/whmcs-database-optimization).

## Signs the problem is in the runtime

- Even simple pages take a long time before the first byte arrives
- Accepting an order or running a module command ends in a timeout
- Automation Status turns yellow because the cron overlaps its next run or dies with memory or execution time errors
- Load spikes at a predictable time, often when the daily cron or a database backup runs
- System Health shows warnings about PHP memory, error levels, sessions or OPcache

## What we review and adjust

### PHP

- **Version.** The 8.13 branch accepts PHP 8.1 to 8.3, while the 9.x branch requires 8.2 at minimum and accepts up to 8.4. We match the newest version your WHMCS release, ionCube Loader and third-party modules all support, and keep the cron on the same binary.
- **Handler and pool.** PHP-FPM or LiteSpeed's LSAPI with a pool that runs as the account owning WHMCS, sized so busy periods queue briefly instead of failing.
- **Limits.** memory\_limit at WHMCS's recommended 128 MB or above, and max\_execution\_time long enough for module calls and large reports.
- **OPcache.** WHMCS strongly discourages it because it can keep serving stale code, so we switch it off for the PHP pool that runs WHMCS rather than tuning it.
- **Sessions and errors.** A writable session save path, session autostart off, and production error levels that log problems without printing them to customers.

### The system cron

- A five-minute schedule run from the command line, as our [cron troubleshooting guide](/blog/whmcs-cron-not-running) explains
- A verbose run to see which tasks take longest, such as UpdateServerUsage, TenantUsageMetrics or SslSync
- Servers in Configuration &gt; System Settings &gt; Servers that no longer answer, which make usage updates wait on network timeouts
- Where it helps, the cron's skip and do arguments to move one heavy task to a quieter hour
- The built-in database backup task, which WHMCS notes is CPU, memory and disk heavy, moved off the busy daily run or replaced by a server-level backup

### Web server and host

- Apache with the event MPM, LiteSpeed, or Nginx (which WHMCS supports only on a limited basis), with keep-alive and worker counts that fit the RAM you have
- CloudLinux LVE limits that throttle the WHMCS account, and the nd\_pdo\_mysql extension WHMCS asks CloudLinux users to enable
- CPU steal, swap use and disk wait on the VPS, which no PHP setting can fix
- Outbound calls to registrars, provisioning panels and gateways, timed through the Module Log, which we switch on only for the test because debug logging grows the database fast

## Settings WHMCS does not offer

Earlier versions of this page promised Redis queues and parallel cron workers. WHMCS has no documented setting for either, and bolting them on risks the stale-data problems WHMCS warns about with OPcache. We stick to configuration WHMCS documents and supports, so updates and WHMCS Technical Support keep working for you.

## How the job runs

1. Baseline: first-byte times for admin and client pages, cron run duration from the Activity Log, and the server's load graph.
2. Changes one at a time, with copies of every php.ini, pool and web server file we touch, in a window you approve.
3. The same measurements again, written up side by side.

## What we need

- Root or sudo SSH, or administrator access to WHM, Plesk or DirectAdmin
- A WHMCS admin login
- A quiet period for PHP and web server restarts

## Prices

ScopePricePHP, web server and cron tuning for one install on one serverFrom $149A separate database server, a load balancer or several installsFixed quoteA slow custom module or hook that needs code changes$65/hour or fixed quote

Fixed-price work is billed half up front and half when it is delivered, and fixes to anything we changed are free for 14 days.

## Outside the scope

- Hardware upgrades or hosting fees
- Rewriting slow third-party modules; old code that breaks on newer PHP is [legacy module rescue](/services/whmcs-legacy-module-rescue)
- Moving WHMCS to a new server

If you already have a slow cron run's output or a page timing, attach it to your [project request](/start-project) and we will read it before we speak.

## What's included

- PHP version matched to your WHMCS release, ionCube Loader and modules
- PHP-FPM or LSAPI pool sized for the account that owns WHMCS
- memory_limit, max_execution_time, session and error settings checked
- OPcache switched off for WHMCS, as WHMCS recommends
- Verbose cron run to find the slowest tasks
- Dead or unreachable servers removed from usage updates
- Heavy tasks moved with the cron's skip and do arguments where useful
- Web server workers, keep-alive and CloudLinux limits reviewed
- Before-and-after measurements of first-byte time and cron duration

## Business outcomes

- Admin actions such as order acceptance finish instead of timing out
- The daily cron completes well before the next run
- Predictable load spikes are explained and moved or removed
- Your setup stays within what WHMCS documents and supports
- You get a record of every server file changed, so it can be reversed

## Frequently asked questions

### Does WHMCS support Redis or OPcache?

WHMCS has no documented Redis setting, and it strongly discourages OPcache because cached code can go stale. Our work concentrates on PHP settings, web server workers and cron scheduling.

### Which PHP version should WHMCS use?

WHMCS 8.13 supports PHP 8.1 to 8.3 and WHMCS 9.x supports PHP 8.2 to 8.4. The right choice is the newest one your ionCube Loader and third-party modules also support.

### Can I run WHMCS on Nginx?

Yes, many installs do, but WHMCS validates on Apache and offers only limited help for Nginx. We tune whichever you run and keep the directory protections WHMCS relies on.

### Do you need root access?

Root or sudo gives the most room, because pool and web server settings live there. With control panel access only, we tune what the panel exposes and list what your host would need to change.

### How much does performance tuning cost?

From $149 for one install on one server. Separate database servers, load balancers and code changes are quoted after the free scoping call.

### Will customers notice the work?

Only briefly, if at all. PHP and web server restarts happen in a quiet window you approve, and each change is made separately so it can be reversed.
