Correct production concurrency documentation

[fabmnt]

Summary

• correct the documented production collection concurrency from four to three
• record the limits actually visible to Node at runtime: 8 CPUs and 7.5 GiB

Context

After PR #11 merged, the production backend started successfully and logged:

Collection worker concurrency set to 3 (8 CPUs and 7.5 GiB memory)

Railway's dashboard metric rounds/reports the memory allocation differently. The implementation is behaving as designed: after reserving 1.5 GiB and budgeting 1.5 GiB per collection, the runtime limit safely selects three concurrent jobs.

Validation

• pnpm exec prettier --check README.md
• git diff --check

Summary by CodeRabbit

• Documentation
  • Updated Railway deployment guidance for how COLLECTION_CONCURRENCY is auto-sized based on the runtime’s provided resources (8 CPUs and 7.5 GiB), resulting in selecting three concurrent collections.
  • Corrected prior guidance that indicated a larger allocation and up to four concurrent collections.
  • Noted that startup logs report the detected limits and chosen concurrency, with memory rounded to one decimal place.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 10141921-4366-4d19-84e0-190f642f78dc

📥 Commits

Reviewing files that changed from the base of the PR and between 032f282 and b35036e.

📒 Files selected for processing (1)

• README.md

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

---

📝 Walkthrough

Walkthrough

The README documents Railway’s 8 CPUs and 7.5 GiB provided to Node, automatic selection of three concurrent collections, and startup logging of detected limits and concurrency.

Changes

Railway concurrency documentation

Layer / File(s)	Summary
Document Railway auto-sizing README.md	Updates Railway resource details and automatic concurrency selection, and documents the worker’s startup logging.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• fabmnt/media-scraper#11: Implements the resource-based COLLECTION_CONCURRENCY auto-sizing behavior documented here.

Poem

I’m a rabbit with three carrots to spare,
Eight CPUs humming in the air.
Seven-point-five gigs glow bright,
Startup logs make limits right.
Hop, hop—concurrency’s there!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is clearly related to the main change: correcting production concurrency documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/correct-production-concurrency

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 95: Update the README concurrency example to match the worker’s
documented formula: with 8 CPUs and 7.5 GiB, state that automatic concurrency
selects four collections, unless the implementation is intentionally changed to
produce three.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3bd2435d-5443-4a28-8c34-0c41d099b50a

📥 Commits

Reviewing files that changed from the base of the PR and between d6878d4 and 032f282.

📒 Files selected for processing (1)

• README.md

[Copilot]

Pull request overview

Updates runtime/concurrency documentation in the repository README to reflect the production backend’s observed collection concurrency and the resource limits visible to Node at startup.

Changes:

• Corrects the documented production collection concurrency (from four to three).
• Records the runtime-reported CPU/memory limits (8 CPUs and ~7.5 GiB) as observed in worker startup logs.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.