Web hosting
Hosting memory limits: PHP memory, process RAM and account limits are different
Shared-hosting memory limits constrain the memory an account’s processes can consume on a multi-tenant node. Memory errors can be caused by PHP memory_limit, concurrent workers, large imports, image processing, plugins, cron, or per-account resource controls; the exact layer matters.
Identify PHP versus account/system memory limit
A PHP fatal “Allowed memory size exhausted” points to the per-process PHP memory_limit; a hosting resource fault may indicate aggregate account usage across processes. Read both application logs and hosting resource metrics.
Raising PHP memory_limit lets one process grow but can worsen aggregate pressure if many workers run concurrently.
Find the operation allocating memory
Large image manipulation, backups, CSV imports, report generation, page builders, plugins, and poorly bounded queries are common. Reproduce in a controlled window and profile the operation.
Process the dataset in batches where software supports it.
Reduce concurrency or per-process use
Tune PHP workers, plugin behavior, image sizes, caches, and cron concurrency. Remove abandoned plugins/themes and investigate memory leaks/repeated growth.
Keep enough memory headroom for normal spikes and system services.
Upgrade when healthy working set exceeds shared boundaries
A VPS provides a dedicated memory allocation but also transfers operating-system administration to the customer. Choose it when the application needs that resource/control boundary, not merely to avoid fixing a leak.
- Locate the memory limit layer.
- Profile the allocating task.
- Bound concurrency and batch work.
- Upgrade for sustained healthy demand.