0.3 GB idle, against 0.43 to 1.8 GB.
A host packs mostly-idle sites onto each server. Thirty seconds after a load stops, four BookPress workers release to about 0.3 GB; a right-sized WordPress holds 0.43 GB and a tuned 64-child pool holds 1.8 GB. Under load BookPress uses about 0.6 GB, close to the right-sized pool that serves fewer pages. Memory for every configuration →
We measured the same site, all plugins active, on the Intel server 30 s after the full load run. We count memory shared between processes once. The run used BookPress 0.2.57, 13 October 2026.
Memory for every configuration.
A host sizes a server by memory. We measured both stacks under full load and again 30 seconds after the load stopped, on the same site with all plugins active, counting memory shared between processes once. We ran WordPress two ways so pool size does not rig the comparison: a tuned static 64 children pool and a right-sized dynamic, 8 children pool. We measured memory on BookPress 0.2.57.
Intel server (4 vCPU)
| Configuration | Memory, under load | Memory, idle 30 s |
|---|---|---|
| BookPress (4 workers) | 595 MB | 319 MB |
| WordPress (8 PHP children, right-sized) | 525 MB | 432 MB |
| WordPress (64 children, tuned) | 1784 MB | 1782 MB |
ARM server (4 vCPU)
| Configuration | Memory, under load | Memory, idle 30 s |
|---|---|---|
| BookPress (4 workers) | 688 MB | 299 MB |
| WordPress (8 PHP children, right-sized) | 528 MB | 435 MB |
| WordPress (64 children, tuned) | 1803 MB | 1802 MB |
We measured memory on BookPress 0.2.57, 13 October 2026. WordPress ran PHP-FPM with OPcache and JIT, MariaDB, a Redis object cache and nginx. Neither side used a page cache. The throughput figures on the speed page are a later and separate measurement, on BookPress 0.2.64.
Idle is the density figure. Thirty seconds after the load stops, four BookPress workers release to about 0.3 GB; a right-sized WordPress holds 0.43 GB and a tuned 64-child pool holds 1.8 GB. A host packs mostly-idle sites, so the memory a site hands back between visitors is the memory another site can use.
More workers. Engine code and plugin bytecode load once, and every worker shares them. Each additional worker then adds its own working set under load and gives most of it back when idle. A worker that has had no request for 30 seconds gives memory back to the system; a WordPress pool holds what it preforked.
Workers sized to the machine.
BookPress sets its number of workers from the machine's processors and memory when it starts. Every worker shares the engine code and plugin bytecode. Each worker then adds its own working set under load and releases most of it when idle. A worker is a core's worth of serving capacity. We measured the memory figures on this page with four.
✓ Workers you size
If you set a number of workers, BookPress uses it. We measured the figures on this page with four: about 0.6 GB under load, releasing to about 0.3 GB 30 seconds idle.
✓ No database server
Storage is embedded SQLite on the same WordPress schema, in-process. On the WordPress side MariaDB alone holds 0.2 to 0.4 GB, depending on its buffer pool.
✓ No cache tiers
BookPress runs with no object cache and no page cache. It rendered each page in these figures from scratch.
✓ One binary
The server is one 1.8 MB program. Its workers load it once and share it.
BookPress gives memory back between visitors.
Under load the same site takes about 0.6 GB on four BookPress
workers, close to a right-sized WordPress and a third of a tuned pool. Idle, it releases
to about 0.3 GB while the WordPress pools hold. The saving across many sites comes from this idle release. The sites keep their themes, /wp-admin and URLs.
If you run the servers
BookPress is software you run on your own infrastructure. You import a site from a standard MySQL dump and can export it the same way.
If a host runs them for you
BookPress Hosting runs your WordPress sites on the engine for you, on servers in Germany. You keep wp-admin; we do the patching and the backups.
Licensing
We license the engine to platforms from 10,000 sites, with our team alongside yours while you roll it out.
Measure it on your own sites
Tell us how many sites you run, which plugins are on them, and where you host them today. We'll measure memory with you on your own hardware.
[email protected]