letsencrypt / letsencrypt/boulder
mtca: improve tile writing performance
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
As of #8896, Frontier.Flush() writes tiles serially with no retries. Ideally we should write tiles in parallel, have per-attempt timeouts shorter than the overall context deadline, and do retries. Since tile writing is on the sequencing path, this will strongly influence how long sequencing takes, which in turn influences how frequently we can sequence.
Part of #8738
Contributor guide
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
Start at Frontier.Flush and review the context from #8896 and the broader work in #8738. Determine how tile writes currently occur on the sequencing path, then define completion around parallel writes, per-attempt timeouts shorter than the overall deadline, and retries without delaying sequencing unnecessarily.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100