Azure / Azure/bicep

Bicep restore should restore modules concurrently

Open
#4,787 1 comment 1 reaction 0 assignees View on GitHub
enhancement story: registry
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

Module restore is currently done sequentially. We need to do it concurrently with some limit on how many can be done at the same time. This will improve restore latency.

Contributor guide

Open the contributing guide

Research direction

Start by locating the module restore entry point and tracing how modules are currently restored sequentially. Define a bounded concurrency approach and verify that the restore path limits simultaneous work while reducing restore latency; the issue does not name specific files or tests.

Written by the indexing model from the issue text.

Assessment

Domain
performance, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.