Perf/api load testing and scaling plan - #365
Merged
jotel-dev merged 5 commits intoJul 30, 2026
Merged
Conversation
|
@extolkom is attempting to deploy a commit to the jotelfootball-tech's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
@extolkom you did a very good job 👍 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #40
Load Testing Tooling & Test Scenarios:
Enhanced
k6-load-test.js
with explicit Baseline Load (1 VU), Ramp-Up (10 -> 50 VUs), Sustained Soak Test (50 VUs constant), and Spike Test (250 VUs burst) scenarios.
Updated
run-load-test.js
native runner to capture response latencies (p50/p90/p95/p99), RPS, and error rates, outputting structured metrics to
load-test-results.json
.
Bottleneck Analysis:
Soroban RPC Contention: Monotonic sequence number collisions (txBAD_SEQ), synchronous simulation delays (~1–2s), and worker thread blocking during ledger polling (15s–45s).
Database & Storage Layer: In-memory Map state (store.ts) causing split-brain when horizontally scaling, lack of connection pooling (PgBouncer needed).
Fastify Error Handler: @fastify/rate-limit throwing standard JS errors that fall through to 500 internal server error blocks instead of returning HTTP 429.