WP49: async/await on the server, and the TechEmpower top
State: In progress · Done: 4 of 6 · Design note: docs/wp49-async-server.md
Stages
- Stages 1 to 3: the renames,
nish/net/upstream, the Postgres pool and carrier, every TechEmpower test type - Stage 4:
async,await,Promise<T>,spawn,awaitAll, the frame lowering - Stage 5: the executor, async
fetchover TLS,serve, the async Postgres pool, cancellation, tasks reaching their spawner's objects (#1343) - Stage 6: the async TechEmpower entries, measured (#1367)
- Stage 6: the gate, the async entries within the explicit ones' noise band on
plaintext,jsonanddb - Submit to TechEmpower (open question)
Next
Meet stage 6's gate. The latest measurement (2026-11-14, after the resume build #1621) has 4 of the 11 judged cells inside: plaintext 256/1024/4096 and json 16/256 are outside, and json 32 and 512 cannot be judged in that container. #1621 cut the async entry's peak RSS at plaintext 16,384 connections from 32.4 to 26.9 MiB. The async entry still runs about 2,054 more instructions a request than the explicit one on plaintext and 2,425 on json: the second task per request (about 425), the router (about 455 and 348) and serveTask's request copy (about 378).
Open questions
D6: whether and when to submit, shared with WP39 E9.
Not planned
Promises as values, for await. async on the wasm profile is WP54's, proposed.

