Fix XLSX ingestion memory spikes with streaming parser#1
Merged
Conversation
plasma16
force-pushed
the
fix/xlsx-memory-spike
branch
from
9075e4c to
c3a1f11
Compare
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.
Summary
.xlsxconversion through a streamingopenpyxlreader (read_only=True,data_only=True)max_rows=5000,max_cols=64) to prevent pathological worksheet ranges from exploding memoryWhy
Some workbooks report huge used ranges (e.g.
max_row=1048571) despite having very little real data, which can cause generic converters to consume excessive RAM.Result
Significantly lower memory use during XLSX ingest while preserving useful sheet content for KB compilation.