New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tesseract OCR is excessively long on quad-core CPU #3

Closed

davidbernard04 opened this issue Feb 1, 2022 · 1 comment · Fixed by #4

Labels

Owner

davidbernard04 commented Feb 1, 2022

Seems like a known issue with Tesseract 4.x and Tesseract 5.x, as per tesseract-ocr/tesseract#263 (comment)

The proposed fix is to disable multi-processor in Tesseract.

Owner Author

davidbernard04 commented Feb 1, 2022

Using only 1 thread greatly reduced OCR delay!

On a AMD FX-4100 (quad-core 3600Mhz):

Before: 25 sec
Now: 1 sec

davidbernard04 added bug enhancement and removed bug labels

davidbernard04 mentioned this issue

Limit OCR to only 1 thread. #4

Merged

davidbernard04 closed this as completed in #4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment