Repository navigation
Replies: 4 comments
posix-kernel with #4469#4469 boots from the installed database, probes the server with Median of 5 rounds, min–max in parentheses.
|
posix-kernel with Automattic/kandelo#1545
Medians of 2 alternating passes of 3 rounds (pass 1 / pass 2):
|
posix-kernel with Automattic/kandelo#1545 on PHP 8.5.12Kandelo
Median of 5 rounds, min–max in parentheses.
Syscalls for one warm REST request, from the Playground CLI on Node with
|
posix-kernel with MariaDBThis run replaces SQLite with MariaDB in posix-kernel and compares it with classic on SQLite. classic cannot run MariaDB: php.wasm has no processes and no sockets.
Median of 5 rounds, min–max in parentheses.
Against posix-kernel with SQLite from the previous comment, measured on another day:
MariaDB adds about 0.2 s to the boot, 4 MiB to the download and 600 MiB of memory. It makes REST requests about 12 ms faster and front page loads about 16 ms faster. The kernel, not the database, causes most of the gap to classic. Setup:
Memory of posix-kernel grows between rounds: 3885 MiB in round 1, about 4450 MiB in rounds 2 to 5. Memory of classic stays flat. The cause is not known yet. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
How fast WordPress loads in the browser on three runtimes. Each new run gets its own comment.
?experimental=kandelo([wasm-posix-kernel] WordPress Playground Web Kandelo Beta - Proof of concept #3957).wordpress-sqlite.Results
Run of 2026-10-19. Median of 5 rounds, min–max in parentheses. Lower is better.
Metrics
Each round starts a new Chromium with an empty cache and empty storage.
page.goto()until the WordPress front page renders.page.reload()until the front page renders again, with a full HTTP cache.wp-admin/until the admin bar renders, logged in.fetch()calls to?rest_route=/wp/v2/posts.Setup
Production builds served from localhost, with the deployment headers of each target. Apple M4 Max, Chromium.
All reactions