FHIR Server Performance Benchmark

Reports

FHIR Servers

• Aidbox — JVM, PostgreSQL
• HAPI FHIR — JVM, PostgreSQL
• Medplum — Node.js (×8 replicas), PostgreSQL + Redis
• Microsoft FHIR — .NET R4, SQL Server 2022
• WSO2 FHIR — Go, PostgreSQL
• InterSystems IRIS for Health — Community Edition, embedded IRIS database

Aidbox, HAPI, Medplum and WSO2 share one PostgreSQL instance (a database per server). The Microsoft FHIR server only supports SQL Server, so it runs against its own dedicated SQL Server. InterSystems IRIS for Health stores FHIR data in its own embedded database, so it is a single container. Tests run sequentially, so only one server + database pair is under load at a time.

Local development

./runner.sh bootstrap

Open http://localhost:13080 and activate Aidbox.

Infrastructure

Services	Local address	Internal address
Aidbox	http://localhost:13080	http://aidbox:8080
HAPI	http://localhost:13090	http://hapi:8080
Medplum	-	http://medplum:8103
Microsoft FHIR	http://localhost:13100	http://microsoft:8080
WSO2 FHIR	http://localhost:13110	http://wso2:9090
InterSystems IRIS for Health	http://localhost:13120/fhir/r4	http://intersystems:52773/fhir/r4
Grafana	http://localhost:13000	http://grafana:3000
Prometheus	http://localhost:13010	http://prometheus:9090

InterSystems IRIS for Health serves only metadata without authentication; use HTTP Basic auth fhir / fhir.

Running benchmarks with runner.sh

runner.sh is the entry point for bringing up the stack and running the k6 load tests. Each test runs inside the k6 container and streams its results to Prometheus via remote-write, so you can watch them live in Grafana.

Bootstrap the stack

Pull images and start all services (FHIR servers, databases, monitoring):

./runner.sh bootstrap

Run a test

./runner.sh -t <test> [-s <server>] [-id <runId>] [-f <compose-file> ...]

Flag	Description
-t	Test file to run: /k6/prewarm.js, /k6/crud.js, /k6/import.js, /k6/search.js (default: /k6/prewarm.js)
-s	Target server: aidbox, hapi, medplum, microsoft, wso2, intersystems. Omit to run on all servers sequentially
-id	Run ID that tags the metrics. Defaults to the current UTC timestamp (or the RUNID env var)
-f	Extra Docker Compose file(s); repeatable. Defaults to docker-compose.yaml

The -s/fhirimpl tag and -id/runid tag are what the report snapshot later queries from Prometheus, so keep the same -id across a run's tests.

Examples

# Full run against every server (prewarm, then the three suites)
./runner.sh -t /k6/prewarm.js
./runner.sh -t /k6/crud.js
./runner.sh -t /k6/import.js
./runner.sh -t /k6/search.js

# CRUD on Aidbox only, with a custom run ID
./runner.sh -t /k6/crud.js -s aidbox -id my-test-run

# Reuse one run ID across suites so they land in the same report
RUNID=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
./runner.sh -t /k6/crud.js   -id "$RUNID"
./runner.sh -t /k6/import.js -id "$RUNID"

Run ./runner.sh -h for the full built-in help. Turning the collected metrics into a report is done separately — see scripts/generate-snapshot.js.

Coverage

CRUD

• Create
• Read
• Update
• Delete

Bulk import

• FHIR bundle

Search

• Simple search (string, date, token, quantity)
• Complex search (composite, reference, modifiers, prefixes)