implemented ability to limit number of threads used by tesseract #123
Conversation
This file contains 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
that may be used by tesseract.
Repository owner
deleted a comment
May 11, 2018
Repository owner
deleted a comment
May 11, 2018
Repository owner
deleted a comment
May 11, 2018
Repository owner
deleted a comment
May 11, 2018
|
Hallo @suud thank you very much for finding that out and contributing back! is a really nice addition to the library, will merge and bump the version to make it already available ;D |
|
FYI, I needed to move |
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.
Running multiple content-extraction-jobs in parallel on one machine leads to an enormous increase of execution time (see tesseract-ocr/tesseract#1019). One solution is to limit the number of threads usable by tesseract. If you have 4 cores and limit the number of threads used by tesseract to two, two parallel extractions are working fine.
Sadly, there is no built-in option for tesseract to limit the number of threads. But it's possible to do so with the OMP_THREAD_LIMIT-command.
Grüße nach Berlin!