Flow — Performance Report
Date: March 8, 2026
Target: https://api.rynko.dev/api (production)
Suite: Rynko Performance Suite v1.0.0
Result: 5/5 tests passed, 0 SLA breaches
What Was Tested
The Flow performance suite was run against Rynko's production API — 5 tests covering gate listing, run submission latency, end-to-end validation lifecycle, throughput, and listing operations. All tests used a real Flow gate with schema validation and business rules.
Gate Operations
Latency for listing and retrieving Flow gates, measured over 50 iterations.
Gate Listing Latency (PERF-050)
| Metric | Value |
|---|---|
| P50 (median) | 310ms |
| P95 | 327ms |
| P99 | 497ms |
| Mean | 315ms |
| Min | 293ms |
| Max | 654ms |
| Std Dev | 49ms |
Gate listing includes fetching all active gates with their schemas, business rules, and configuration. The tight distribution (4ms std dev excluding outliers) shows consistent performance.
Run Submission
Submission Latency (PERF-051)
Time to submit a payload to a gate and receive the validation response, measured over 50 iterations. This measures just the submission — no polling.
| Metric | Value |
|---|---|
| P50 (median) | 332ms |
| P95 | 353ms |
| P99 | 392ms |
| Mean | 336ms |
| Min | 321ms |
| Max | 396ms |
| Std Dev | 14ms |
The 14ms standard deviation means run submission is highly consistent — schema validation and business rule evaluation add minimal overhead to the base API latency.
End-to-End Performance (PERF-052)
Complete run lifecycle from submission to terminal state (validated/completed). For auto-approved gates, this measures submit → schema validation → business rule evaluation → status resolution.
| Metric | Value |
|---|---|
| P50 (median) | 332ms |
| P95 | 386ms |
| P99 | 423ms |
| Mean | 338ms |
| Min | 316ms |
| Max | 429ms |
| Std Dev | 22ms |
The end-to-end time is nearly identical to submission latency, which means validation completes synchronously within the request — no background processing or polling required for standard validation runs.
Throughput (PERF-053)
Sustained run submission rate measured over a 30-second window at concurrency 5.
| Metric | Value |
|---|---|
| Total Requests | 445 |
| Successful | 445 |
| Failed | 0 |
| RPS | 14.64 |
| Error Rate | 0.00% |
At 14.64 runs per second, Flow can handle ~879 validations per minute or ~52,700 per hour without errors. This is well within the capacity needed for most agent workflows.
Listing Operations (PERF-054)
Latency for listing runs, active runs, and approvals — the read operations teams use for monitoring and dashboards.
| Metric | Value |
|---|---|
| P50 (median) | 321ms |
| P95 | 411ms |
| P99 | 424ms |
| Mean | 340ms |
| Min | 297ms |
| Max | 429ms |
| Std Dev | 39ms |
Summary
| Operation | P50 | P95 | Error Rate |
|---|---|---|---|
| Gate Listing | 310ms | 327ms | 0% |
| Run Submission | 332ms | 353ms | 0% |
| Run End-to-End | 332ms | 386ms | 0% |
| Run Throughput | — | — | 0% (14.64 RPS) |
| Listing (runs/approvals) | 321ms | 411ms | 0% |
Test Configuration
target:
baseUrl: https://api.rynko.dev/api
timeout: 60000ms
execution:
iterations: 50
concurrency: 5
loadDurationSeconds: 30
targetRps: 20
sla:
maxP95LatencyMs: 1000
maxP99LatencyMs: 2000
maxErrorRate: 0.05
minThroughputRps: 10
Key Takeaways
- Sub-400ms validation at p95 — schema validation and business rule evaluation complete within a single HTTP round trip. No background processing needed for standard runs.
- 14.64 RPS sustained throughput — enough for ~52,700 validations per hour with zero errors.
- Consistent performance — standard deviation of 14–49ms across all tests shows predictable latency regardless of load.
- Synchronous validation — end-to-end time matches submission time, confirming that validation is not deferred to a background queue. Agents get immediate feedback.