Repository navigation
perf(office): index ZIP part names for conversion - #979
Merged
Merged
Conversation
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
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.
Office documents with many parts repeatedly scanned every ZIP entry when resolving slides, relationships and missing optional parts. Index decoded exact names and build the ASCII case fallback once, while preserving exact-case precedence, leading slashes and existing container limits.
On synthetic decks with 3,000 slides and 9,002 ZIP entries, 35 alternating release-mode conversion measurements per version improved the median from 73.7 ms to 44.1 ms (1.67×). Complete serialized output matched for 10, 100, 1,000 and 3,000 slides. These local measurements do not establish a production workload or a general speed guarantee.
Validation: