ProcessWire and Shared Hosting: Optimizing Resource Footprint for Low-Traffic Workloads

ProcessWire is designed as a lightweight CMS, often making it a viable candidate for low-cost shared hosting environments. To minimize operational costs, it is necessary to reduce the CPU and memory overhead associated with each request.

The system utilizes an internal caching layer to limit SQL queries and a flat-file configuration approach for core metadata. However, resource consumption fluctuates based on the number of active modules and the depth of the page tree hierarchy. In environments with strict PHP memory limits, there is a trade-off between utilizing comprehensive admin modules and maintaining a lean front-end delivery profile.

When targeting the lowest possible resource tier, it is unclear which specific module configurations or page tree structures most significantly impact the baseline memory footprint during a standard page request.

• Which specific active modules typically contribute the most to baseline PHP memory usage in a default installation?
• Does the complexity of the page tree hierarchy linearly increase the memory overhead during the initial page load process?