Database Test Profiles
Database profiles measure the whole path from request to query and back: the framework, its Postgres driver and any data-access layer on top. They run over HTTP/1.1 with the same load generator as the H/1.1 profiles, but rank on their own board, because the database and its driver dominate these numbers far more than the framework does. Both profiles count toward the Database composite.
CPU layout
Postgres does real work here, so the box is split three ways instead of two. Every core is paired with its SMT sibling.
| Role | Logical CPUs | Cpuset |
|---|---|---|
| Server | 32 | 0-15,64-79 |
| Load generator (32 threads) | 32 | 16-31,80-95 |
| Postgres | 64 | 32-63,96-127 |
The results measured before this split, with Postgres sharing the other two's CPUs, were cleared on 21 November 2026. The board fills up again as entries are re-run.