# Measurement report — SIMYL Research template

Fill in every section. If a value does not exist, write "not available" and explain why; do not leave it out.

## 1. System and scope
- System or component measured (name, version, commit):
- Question this measurement answers:
- Kind of figure: benchmark / production / estimate (one only):

## 2. Environment
- Hardware (CPU, cores and threads, memory, storage, network):
- Operating system and kernel:
- Power profile or frequency governor (if applicable):
- Runtime, compiler and relevant library versions:
- Configuration of the measured system (parameters, replicas, limits):
- Other processes active during the measurement:

## 3. Load
- Load generator (tool and version) or real-traffic period:
- Key or request distribution, message sizes:
- Concurrency (workers, connections):
- Warm-up (duration), measured period (duration), repetitions:

## 4. Procedure
Exact commands or steps, in order, to repeat the measurement:

```
```

## 5. Results
| Metric | Unit | Median | Min | Max | Repetitions |
|---|---|---|---|---|---|
| Throughput (requests/s) | | | | | |
| Latency p50 | | | | | |
| Latency p90 | | | | | |
| Latency p99 | | | | | |
| Latency p99.9 | | | | | |
| Maximum latency | | | | | |
| Errors | | | | | |
| CPU | | | | | |
| Resident memory | | | | | |

Location of the raw data (path or link):

## 6. Variability and limits
- Range observed across repetitions and its probable cause:
- What this measurement does not cover (other hardware, real traffic, untested sizes):

## 7. Conclusion
- What is claimed, with the figure and its context:
- What is not claimed:

## 8. Record
- Who measured, date and time (with time zone):
- Total duration of the measurement: