mtca: improve tile writing performance

Open
#8,903 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
backend

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.

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

Dominant language
Go
Stars
5.8k
Forks
649
Avg merge
3d 23h
Merged PRs (30d)
24

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from letsencrypt/boulder

All issues in letsencrypt/boulder

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.