fix: streaming tar extraction for large repo cloning - #862
Merged
Conversation
The git clone implementation was loading the entire decompressed tar archive into memory, parsing all files into a Map, then converting to strings. For large repos like antiwork/gumroad (149MB compressed), this caused ~1.2GB peak memory usage, exceeding Convex's 512MB limit. Rewrote to stream the tar extraction: - Parse tar headers on-the-fly as data arrives - Write files to the virtual filesystem immediately - Only hold one file's content in memory at a time Memory usage reduced from ~1.2GB to ~275MB (4x improvement).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Jan 4, 2026
mrmeomeo-cybersecurity
left a comment
There was a problem hiding this comment.
mrmeomeo-cybersecurity
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
2 participants
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.
Summary
antiwork/gumroadin the AI chat featureProblem
The git clone implementation for the
/chatfeature was loading the entire decompressed tar archive into memory, then parsing all files into a Map, then converting to strings. For large repos likeantiwork/gumroad(149MB compressed, 328MB decompressed, ~4000 files), this caused ~1.2GB peak memory usage, exceeding Convex's 512MB action limit and causing "Transient error while executing action" failures.Solution
Rewrote
git-clone.tsto use streaming tar extraction:Testing
Tested locally with
antiwork/gumroad: