Root-cause slow git clone in Docker sandbox: not reproducible, unblock - #28
Open
nishantkluhera wants to merge 1 commit into
Open
Root-cause slow git clone in Docker sandbox: not reproducible, unblock#28nishantkluhera wants to merge 1 commit into
nishantkluhera wants to merge 1 commit into
Conversation
Full isolation matrix from measured runs: container depth-1 clone 20.1s vs host 29.4s (parity within variance), index-pack dominates at 17.3s, DNS 1-25ms, MTU 1500, HTTP/2-vs-1.1 immaterial, small-repo fixed cost ~1s, full clone 160s/779MB scaling linearly with pack size. The reported 31MB-after-3-minutes profile is ~40x below every measurement taken today on both paths - consistent with a transient upstream/link event, not a bridge defect. Two operational findings folded in: GH_TOKEN alone does not authenticate bare git-over-HTTPS (needs gh auth setup-git or URL- embedded creds - instant failure, not a hang), and --filter=blob:none is strictly SLOWER than plain --depth 1 for a shallow checkout (31s vs 20s; checkout degenerates into lazy per-blob fetches). Recommendation: don't block enablement; use plain depth-1; if the crawl recurs, capture GIT_TRACE_PERFORMANCE + curl -w at that moment per the decision tree in the doc. Closes #10
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Full isolation matrix from measured runs: container depth-1 clone 20.1s vs host 29.4s (parity within variance), index-pack dominates at 17.3s, DNS 1-25ms, MTU 1500, HTTP/2-vs-1.1 immaterial, small-repo fixed cost ~1s, full clone 160s/779MB scaling linearly with pack size. The reported 31MB-after-3-minutes profile is ~40x below every measurement taken today on both paths - consistent with a transient upstream/link event, not a bridge defect.
Two operational findings folded in: GH_TOKEN alone does not authenticate bare git-over-HTTPS (needs gh auth setup-git or URL-embedded creds), and --filter=blob:none is strictly SLOWER than plain --depth 1 for a shallow checkout (31s vs 20s).
If the crawl recurs, capture GIT_TRACE_PERFORMANCE + curl -w at that moment per the decision tree in the doc (mershlab/research/).
Closes #10
Merge order: last in the chain - #27 first, then this.