Skip to content

perf(sync): fetch projects, tasks, labels and sections concurrently - #216

Merged
romaintb merged 1 commit into
mainfrom
feat/concurrent-fetches
Sep 4, 2026
Merged

romaintb merged 1 commit into
mainfrom
feat/concurrent-fetches

Conversation

@romaintb

@romaintb romaintb commented Sep 4, 2026

Copy link
Copy Markdown
Owner

The four fetches ran in sequence, each re-resolving the backend first. Resolve it once and put all four in flight with tokio::join!, so a sync costs one round trip instead of four.

Error handling per entity is unchanged, sections included: it still degrades to an empty Vec rather than failing the whole sync.

Changes

  • Code changes
  • Tests added/updated
  • Docs updated (README/CHANGELOG)

Checklist

  • cargo fmt passes
  • cargo clippy -- -D warnings passes
  • cargo test passes

Related issues

Initially done by @stevenwcarter in #209

@romaintb romaintb self-assigned this Sep 4, 2026
@romaintb romaintb added the feat label Sep 4, 2026
@romaintb romaintb added this to the v0.6.0 milestone Sep 4, 2026
The four fetches ran in sequence, each re-resolving the backend first.
Resolve it once and put all four in flight with tokio::join!, so a sync
costs one round trip instead of four.

Error handling per entity is unchanged, sections included: it still
degrades to an empty Vec rather than failing the whole sync.
@romaintb
romaintb force-pushed the feat/concurrent-fetches branch from 4561e25 to e4288d0 Compare September 4, 2026 11:19
@romaintb
romaintb merged commit 78ec096 into main Sep 4, 2026
8 of 9 checks passed
@romaintb
romaintb deleted the feat/concurrent-fetches branch September 4, 2026 13:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant