Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[New Feature]: Improve performance for Rebuild pipeline #185557

Open
denelon opened this issue Oct 24, 2024 · 1 comment
Open

[New Feature]: Improve performance for Rebuild pipeline #185557

denelon opened this issue Oct 24, 2024 · 1 comment
Assignees
Labels
Area-Rebuild-Pipeline Related to the rebuild pipeline (BCDR) Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Milestone

Comments

@denelon
Copy link
Contributor

denelon commented Oct 24, 2024

Description of the new feature/enhancement

The latest service interruption involved an attempt to run the rebuild pipeline to completely restore the index and build all manifests as a part of the BCDR (Business Continuity Disaster Recovery) process. This run took approximately 21 hours.

This goal of this feature is to reduce the amount of time required to rebuild the WinGet PreIndexed source cache and the package manifests.

Proposed technical implementation details (optional)

No response

@denelon denelon added Area-Rebuild-Pipeline Related to the rebuild pipeline (BCDR) Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. labels Oct 24, 2024
@denelon denelon added this to WinGet Oct 24, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage This work item needs to be triaged by a member of the core team. label Oct 24, 2024
@denelon denelon moved this to In Progress in WinGet Oct 24, 2024
@stephengillie
Copy link
Collaborator

stephengillie commented Oct 24, 2024

On the spectrum between BC and DR, it sounds like we're way too far over on the DR side, and this work should push us back towards BC. It's not that data was lost or corrupted. But that the recovery process takes too long, possibly because it requires too much rebuilding or reconfiguration. One way to look at this is that more intermediate steps are needed, usually created by decoupling the existing process steps into more steps. So that recovery can be just re-running the last step or few in the process, or only running the essential steps and skipping non-essential steps.

@microsoft-github-policy-service microsoft-github-policy-service bot removed the Needs-Triage This work item needs to be triaged by a member of the core team. label Oct 24, 2024
@denelon denelon added this to the 1.10 Packages milestone Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Rebuild-Pipeline Related to the rebuild pipeline (BCDR) Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Projects
Status: In Progress
Development

No branches or pull requests

3 participants