Improved performance and lower memory usage during PDF indexing #24
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
… @ 2.20GHz this way than fixed thread_count=4 Also added paths_only option to convert_from_path which can significantly reduce memory consumption for large PDFsˆ
bclavie
approved these changes
Sep 23, 2024
|
Great. Thank you! 😃 |
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.
This is an update version of PR #19. Besides CPU-parallel
pdftoppmimages are buffered usingtempfileinstead of in memory. For large PDFs I have measured significantly lower memory usage (8 GB instead of 16 GB) during indexing.More context under #19