From small application records to large stored objects. Thunder brings together reactor-local processing, dedicated memory arenas, and asynchronous I/O—with writes journaled before acknowledgement.
Record the conditions alongside the numbers, so you can repeat a run and understand what changed.
Release & hardware +
Record the server image tag and digest, client version, CPU model, physical cores, SMT, affinity or quota, and derived reactor count.
Include total RAM, arena bytes per reactor, container memory limits, storage device, filesystem, volume type, and available disk space.
Traffic & client placement +
Capture payload sizes, key distribution, dataset size, read/write ratio, concurrency, and connection count. Separate cached reads from reads that reach storage.
Record client placement and network bandwidth. Watch load-generator CPU and serialization costs so you know whether the client is limiting the run.
Durability & security +
Document when writes are acknowledged, whether data is encrypted at rest, and how connections are secured. Thunder journals before acknowledgement, encrypts stored values, and requires TLS.
Use equivalent conditions when comparing systems.
Duration, latency & errors +
Record warmup, run duration, and repeated runs. Include sustained overwrite and delete activity when it reflects your application.
Report completed operations and bytes per second, p50/p95/p99 latency, timeouts, rejected work, and errors. Preserve variation across runs and check returned data for correctness.