Help center

Home Web Performance Optimisation (WPO)[WPO-015] Check PHP OPcache and code deployments

Web Performance Optimisation (WPO)7 min•Difficulty: Avanzado

[WPO-015] Check PHP OPcache and code deployments

Distinguish disabled OPcache, exhausted memory and stale cached code.

Ingeniería de Rendimiento AnayilUpdated: 2026-10-10

Apply this guide to your situation

This answer covers “[WPO-015] Check PHP OPcache and code deployments”. Read it with the summary and confirm that the symptom and service match what you are experiencing. Available options can vary by plan and account setup.

Before changing anything, note what you expected, what happened and roughly when. Check whether the issue affects one page or the whole service.
Save the full error message and note recent changes. Hide passwords, access codes, personal data and keys before sharing screenshots or logs.
If a step requires administrator access, restarting services or editing server files, stop if you do not administer that server. Send support the service name, error and checks you have already made.

L3 technical diagnosis

Performance / configurationSeverity: Medium; high if conversion or availability is affected

User symptoms

PHP responses are slow or the site keeps running old code after a deployment.

Observed code or message

Low OPcache hit rate; memory nearly full; changes not reflected

Likely root cause

Disabled OPcache, undersized memory, unsuitable timestamp validation or separate pools for multiple PHP versions can cause recompilation or inconsistent state.

Likely-cause and resolution matrix

Follow a branch only when evidence supports it. A symptom may have more than one cause; do not change layers by guesswork.

01Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):

bash

Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

02Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):

bash

Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

03Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):

bash

Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

04Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):

bash

Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

05Professional English translation pending.

Why it can happen: Professional English translation pending.

How to diagnose (read-only):

bash

Professional English translation pending.

Step-by-step resolution:
Professional English translation pending.

Prerequisites

Authorised access to the affected site, repository or service metrics.
A reproducible URL and timestamp; use staging for infrastructure changes.
A backup or rollback method for configuration and deployments.

Important warnings

Inspection commands do not authorise production changes. Do not run load tests or global purges without an approved plan.
Never store private responses in shared caches. Server changes in Anayil Panel depend on the controls available for the service and may require its administrator/provider.

Step-by-step walkthrough

1. Reproduce and narrow the issue

PHP responses are slow or the site keeps running old code after a deployment. Identify the PHP version and SAPI serving the site; inspect effective configuration and statistics through a temporary protected endpoint. Do not expose phpinfo publicly.

bash

php -v; php -i | grep -E 'opcache.enable =>|opcache.memory_consumption =>|opcache.validate_timestamps =>'
# CLI may use a different php.ini from PHP-FPM; verify the web pool too.

Expected output:

Low OPcache hit rate; memory nearly full; changes not reflected

2. Apply the appropriate correction

Ask the operator to confirm OPcache in the web SAPI, memory use and release strategy. For immutable releases, validate timestamp policy and reload the pool only in an approved window; deleting cache files does not fix undersized memory.

3. Verify the experience

Confirm the deployed version through a web request, remove any exposed diagnostic endpoint and review latency, hit rate and pool restarts.

Expected output:

The improvement is reproducible on the affected route and profile with no new functional errors.

Troubleshooting & Solutions

Low OPcache hit rate; memory nearly full; changes not reflected

Root cause: Disabled OPcache, undersized memory, unsuitable timestamp validation or separate pools for multiple PHP versions can cause recompilation or inconsistent state.

Resolution: Ask the operator to confirm OPcache in the web SAPI, memory use and release strategy. For immutable releases, validate timestamp policy and reload the pool only in an approved window; deleting cache files does not fix undersized memory.

Rollback and recovery plan

Roll back only the changed directive, dependency or release using the recorded value. If 5xx errors, data exposure or session failures occur, have the operator disable the new rule and retain redacted logs for analysis.

Related runbooks in this category:

[WPO-001] Separate origin latency from browser delay7 min [WPO-002] Diagnose intermittent latency without mislabeling constant slowness7 min [WPO-003] Reduce redirect chains in the page-load path7 min

Was this technical guide helpful?

Facing a production outage?

Hosting Anayil system administrators can directly intervene on your server infrastructure.

Open Support Ticket at Hosting Anayil