Memory pressure can terminate PHP or application processes and often appears as intermittent 500 errors or failed background work.
Applies to: CloudLinux performance and resource limits
CloudLinux limits protect the shared platform and are burstable ceilings rather than dedicated resources. A limit event is a symptom to investigate; repeated events usually require application optimisation, traffic control or a larger plan.
Before you start
- Open the affected hosting service and note the exact time, URL and operation that was slow or failed.
- Have recent CloudLinux usage, application logs and any monitoring alert available for the same time window.
Work through these checks
- Record the limit time and compare it with PHP fatal errors, application logs and the request or task running then.
- Check the PHP memory setting separately from the account-level physical memory limit; increasing one cannot override the other.
- Identify plugins, imports, image jobs, backup processes or scripts that load excessive data into memory.
- Reduce batch sizes, remove duplicate extensions and update code that holds unnecessary objects or query results.
- Retest under the same workload and confirm both application success and resource usage.
- Move to a larger plan when normal supported workload consistently needs more memory than the account allocation.
Confirm the result
- The same operation completes without another limit event during a comparable test.
- CloudLinux graphs and application logs show which change improved the workload rather than merely hiding the symptom.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| The site is slow but no limit is currently shown. | The event has passed, the bottleneck is remote, or application/database work is slow without reaching a hard ceiling. | Use exact timestamps, request logs and slow-query or application profiling rather than relying on a single live graph. |
| Resource faults return after a temporary improvement. | A cache clear or process restart treated the symptom but did not reduce expensive requests, bots or scheduled work. | Identify the repeating URL, job or query and optimise or rate-limit it before choosing a larger plan. |
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The affected domain and SiteWorx account
- The exact error text and time
- The last change made
- Relevant log lines with passwords and personal data removed
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Change PHP settings
- Fix a 500 Internal Server Error
- Resource limit errors and slow sites
- Diagnose a WordPress plugin or theme conflict
- Understand a CloudLinux CPU limit event
Last reviewed: 2026-07-18.
