Backend services

HTTP services backed by PostgreSQL, each running in the same small, resource-limited container.

About this domain

Every implementation serves the same API (JSON, single and multiple queries, updates, a list endpoint and a JSON POST) against the same PostgreSQL 18 database. The service gets 2 CPU cores and 1 GiB of memory, like a small production pod; the database and the load generator run on separate cores. Results cover throughput, latency at fixed load, CPU per request, memory, cold start and warm-up.

2 runs published

Showing Throughput index in Overall, index, higher is better

Derived from several scenarios

Overall

Summary metrics computed from the scenario medians of this run.

Throughput index

higher is better · Geometric mean of throughput over the six workload scenarios, each relative to the fastest implementation in that scenario of the same run. 100 means fastest in all six; the leader of a run scores below 100 when it does not lead every workload.

Computed: Geometric mean of “Throughput” over JSON, Single query, 20 queries, Updates, List, JSON POST, each relative to the best implementation in that scenario (best = 100). Only an implementation that is best in every one of them reaches 100, and only implementations with a usable result in every one of them get an index.

Derived values are computed from scenario medians and carry no interval. Ranks count all 15 implementations.

Not measured in this run: Soak (5 minutes).

Implementations in this run

15 implementations · 11 scenarios measured. Every page lists all scenarios and metrics of one implementation.