Build Performance & Load Testing Suite

[Kalchaqui]

Issue: Build Performance & Load Testing Suite

Depends on: A deployable backend build (pnpm run build) and a staging/local instance to target

Task Description

Evaluate the backend's performance under realistic workloads to identify bottlenecks before production, focusing on the Agreement API under increasing load and concurrency.

Deliverable

A performance & load testing suite with documented benchmarks and a summary report, kept separate from the Jest unit/integration suites (load tools must not run in the standard CI test job).

Requirements

Measure:

• API response times (create/read/update agreement, GET /agreements/:id/activity).
• Database performance (Supabase query latency under load).
• Concurrent Agreement creation and concurrent Agreement updates.
• Activity logging throughput.
• Memory consumption and CPU utilization.

Generate a performance report summarizing results.

Validation System

• Load runs complete against staging and produce metrics for each measured area.
• A performance report is generated with average response time, peak latency, failure rate, and resource utilization.
• Results establish a documented baseline for future comparison.

Technical Requirements

Simulate workloads including:

• 100 concurrent users.
• 500 Agreements and 1,000 Agreements datasets.
• Burst traffic scenarios.

Tooling & constraints:

• Use a Node-friendly load tool (k6, autocannon, or artillery) under a dedicated test/load/ (or perf/) directory with npm scripts (e.g. test:load).
• Target a staging instance with a seeded test user/JWT and testnet wallet — never production.
• Mock or isolate outbound Trustless Work calls so load reflects Thalos, not TW rate limits.
• Keep these runs out of the default jest CI job (long-running, environment-dependent); trigger manually or in a separate workflow.

Additional Notes

Objective is a performance baseline for future optimization and production-readiness, not a pass/fail gate on every PR.

Testing (required)

• Load scripts run for each scenario (100 concurrent users, 500 and 1,000 agreements, burst).
• Metrics captured: avg response time, peak latency, failure rate, CPU/memory.
• Scripts live under test/load/ (or perf/) with a test:load script and are excluded from the default CI test job.

Proof of Completion (required)

• Link the merged PR.
• Attach the generated performance report (baseline numbers per scenario).
• Paste an excerpt of the load-tool output for at least the 100-concurrent-users run.
• Confirm (link/diff) the load suite is separated from the Jest CI job.

[Yerickmondra15]

Hi! I’d like to apply for this issue.

I can build a dedicated performance and load testing suite for the Agreement API using a Node-friendly tool such as k6, Artillery, or Autocannon. I’ll cover 100 concurrent users, 500 and 1,000 agreement datasets, concurrent creates and updates, activity-log throughput, and burst traffic scenarios.

I’ll keep the suite isolated from the standard Jest tests and default CI job, add a dedicated test:load script, and configure it to run only against a local or staging environment with seeded test credentials. Outbound Trustless Work calls will be mocked or isolated so the results reflect Thalos performance rather than external rate limits.

I’ll capture average and peak latency, failure rate, Supabase query timing, CPU, and memory usage, then document the setup, results, limitations, and baseline benchmarks in a performance report for future comparisons.

[grantfox-oss]

🦊 GrantFox — @Yerickmondra15 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #70)
2. Your PR will be reviewed by the Thalos-Infrastructure maintainers

Good luck! Track your progress on GrantFox.

[ManuelJG1999]

🎉 Congratulations @Yerickmondra15 ! This issue has been assigned to you.

Before you start, make sure you understand the requirements. If you have any questions, ask us in our community chat:
https://t.me/ThalosOSSCommunity

Please keep us updated on your progress. If there's no activity or communication within 48 hours, the issue may be reassigned to another contributor.

Happy coding, and thanks for contributing to Thalos! 🐉

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@Yerickmondra15's PR #109 was approved and merged by @ManuelJG1999.

🏆 @Yerickmondra15: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (274 total points). Track your full progress on GrantFox.

👏 Great work, @Yerickmondra15! Keep contributing to Thalos-Infrastructure.