dev: Improve export speed with better parallelization#3593
Merged
Conversation
…n community export
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.
Speeds up
generatePubHtmlFilesin the community export pipeline by processing up to 10 pubs concurrently within each batch (previously fully sequential). The main bottleneck was serial network I/O (asset downloads fromassets.pubpub.organd Firebase draft fetches) which now overlap across pubs. TheseenAssetsdedup map andarchiver.append()are both safe for concurrent use in Node's single-threaded model.Changes
runWithConcurrencyhelper that processes pubs with a concurrency limit of 10 (within the existing batch-of-50 structure)[archive]→[communityExport]to match the convention used inaccountExport