oxidecomputer / oxidecomputer/rfd-api
Manage concurrent RFD handling
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 95
- Forks
- 22
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 17
Description
We have seen when processing multiple RFDs that contain a large number of large images (multi-MB images), we are stressing the CPU and memory of an AWS t3.medium. Note that we are not hitting burst CPU caps. There are two issues at root here:
- We over-process RFDs that have included documents that are on the main branch. We should instead be only generating jobs where at least one required file has changed in the RFD's subdirectory.
- PDF generation should use a queue with a maximum concurrent threshold as this is the primary CPU and memory consumer.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the RFD job-generation path and the PDF-generation path first. Confirm that unchanged required files do not create jobs, then verify PDF work is processed through a queue with a maximum concurrency threshold; completion should prevent concurrent large-RFD processing from overloading CPU and memory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, rust
- Domain
- backend, cloud, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100