Repository navigation
Reduce CSV conversion memory while preserving upstream output - #13
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Large CSV conversions retained every parsed row and a separate list of formatted rows before constructing the complete Markdown. Both normal and archive document engines now use a row-at-a-time CSV formatter for verified MarkItDown 0.1.8/0.1.9, preserving the upstream output and retaining the original converter on unverified versions or a missing helper. The parser-capacity audit records existing limits and the next workbook/native/response-memory boundary; queue concurrency is unchanged.
Three fresh processes per variant, with generated multilingual CSV and identical before/after output hashes: two synchronized 50,000-row conversions used median peak process memory of 297.19 → 221.92 MiB without tracing (about 25% lower), with similar elapsed time. The small fixture's timing regressed; no universal speed, host-capacity or billing claim is made. The full input and output remain materialized.
Validation: