Load Testing & Performance Optimization (Phase 3)

[Cedarich]

Status: Open (Wave 3 – scale)
Labels: Backend, Performance
Complexity: Medium (200 points)
Branch: feat/perf-audit-wave3

Summary
Ensure the backend can handle the expected traffic growth for Wave 3.
Tasks

• Run load tests (e.g., using k6) against the links and transactions endpoints.
• Identify and resolve slow database queries in Supabase.
• Implement response compression and edge-caching where appropriate.
  Acceptance Criteria
• System maintains <100ms response time under 100 concurrent users.

[Risktaker001]

@Risktaker001 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hello. Can i work on this issue?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Risktaker001 to this issue.

[drips-wave]

Congratulations, @Risktaker001! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @Risktaker001: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @Risktaker001 as part of the Stellar Wave Program's 3rd Wave 🥳

Moderator's reason: [Auto-assessed] The PR #231 comprehensively addresses the issue by implementing response compression, a custom LRU caching service, and a robust k6 load testing suite with CI integration. It also provides a detailed performance optimization guide and SQL indexing scripts to resolve database bottlenecks. The PR has been open for over 24 hours without maintainer objections, and the quality of the contribution is high.

😎 @Risktaker001: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.