Hosting Capacity Results
This page records measured WebBlocks CMS capacity evidence. Read it with Hosting Capacity Validation: a partial qualification supports only the workload it actually ran.
Provisional Measured Profile
The recorded local measurements used CMS 1.73.1, PHP 8.4.2 CLI and an SQLite feature-test environment. They do not qualify a production MySQL/HTTP deployment or later releases automatically.
| Workload | Recorded result | Planning boundary |
|---|---|---|
| Core feature suite | Passed five runs with a 128 MiB PHP memory limit; reported peak 101 MiB | Provisional core candidate; not a production-certified minimum |
| One 24 MP GD image transformation | Worst measured process RSS 312.26 MiB | Plan 512 MiB actual process capacity per simultaneously transforming worker for this workload |
PHP's tracked memory peak does not cover every native GD allocation. The worker profile is separate from PHP memory_limit and from total server RAM, which must also cover the operating system, database, web server and concurrent workers.
Qualification Boundaries
The original raw logs were not retained as an immutable qualification record. Treat these figures as provisional comparisons. They are not a universal resource guarantee or a production certification.
The media measurement used 6,000 × 4,000 pixel images. Compressed upload size alone does not bound decoded image memory. Larger dimensions require additional capacity or an explicitly enforced processing policy; this measurement does not certify arbitrary uploads.
Deployment Validation
Before using a measured value as a production requirement, run the complete Hosting Capacity Validation workload on the target PHP web runtime, Laravel application, MySQL database and filesystem. Include installation, updates, backup/restore, transfers, disk limits and concurrent traffic. Retain the raw measurements outside public documentation and publish a reviewed workload summary.
Use Hosting Requirements and the Hosting Readiness Checklist for deployment decisions.