Matchmaking cron scans `queue` table every 10s — query plan is full scan + sort

[mercy60]

Internal ID: #98

Imported from ISSUES.md via scripts/import-issues.mjs.

Problem Statement. MultiplayerQueueService::processMatchmaking:

const waitingPlayers = await this.queueRepository.find({
  where: { status: QueueStatus.WAITING },
  order: { createdAt: "ASC" },
});

No index on (status, createdAt) is mentioned in the entity. With 10k queued users, it's a full table scan every 10 seconds.

Expected Outcome.

• Index on (status, created_at).
• Matchmaking limited to N oldest waiters, e.g. 200.

Acceptance Criteria.

• 10k rows, cron completes in < 200ms.

Files / modules affected.

• backend/src/multiplayer-queue/entities/queue.entity.ts

Dependencies. None.

Difficulty / Effort. Medium / S (≈ 3 hours).

Labels. area:backend, performance, priority:high

[yusufmuhammadayodeji-netizen]

@yusufmuhammadayodeji-netizen has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello, I’ve gone through the requirements and I’m confident I can implement a proper solution that matches the acceptance criteria. Kindly assign this issue to me.

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

[Osuolale1]

@Osuolale1 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I have experience with NestJS, PostgreSQL, and query optimization. I’ll optimize the matchmaking query with appropriate indexing, validate performance improvements, and add tests to ensure scalable, reliable behavior.

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

[Penielka]

@Penielka has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

can be assigned this

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

[Caneryy]

@Caneryy has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi, I'd like to work on this issue please.

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

[drips-wave]

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

🧑‍💻 @Penielka: 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 completed by @Penielka as part of the Stellar Wave Program's 7th Wave 🥳

😎 @Penielka: 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. You can also Leave a review to share your experience working on this issue.

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