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.
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Current logic automatically determines batch ratio based on available VRAM. For certain complex, scanned PDFs, higher batch ratio leads to NPU OOM. Unclear if this is an issue with CUDA-based acceleration
Modification
Added an env var "MINERU_OVERRIDE_BATCH_RATIO" to tune batch ratio manually. Alternatively we can also change this to a ratio to be multiplied by vram-based batch ratio.
BC-breaking (Optional)
No - no backwards compatibility issue (unless MINERU_OVERRIDE_BATCH_RATIO is already used for some other application)
Use cases (Optional)
Processing scanned pdfs with high resource consumption
Checklist
Before PR:
After PR: