Tesseract 4.1 disabled openmp support by default - What does it mean?

42 views
Skip to first unread message

Sarath C P

unread,
Sep 30, 2020, 6:37:57 AM9/30/20
to tesseract-ocr
Hi, we were using Tesseract4.0 in my previous problem. It was giving a good performance when giving  os.environ['OMP_THREAD_LIMIT'] = '1'.

We are planning to upgrade this Tesseract4.1. In the release notes I can see an announcement like" Disable OpenMP support by default"

What does it mean?

1. Does it mean we don't need to take care of this OMP_THREAD_LIMIT? it is in default single threaded execution. But why then performance issue while comparing with tesseract 4.0?


Amit Shah

unread,
Oct 1, 2020, 7:33:28 AM10/1/20
to tesser...@googlegroups.com
Well technically it seems that is what they try to mean - they removing the openmp that was used cuz anyways it was not giving any good results as such.

--
You received this message because you are subscribed to the Google Groups "tesseract-ocr" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tesseract-oc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-ocr/980dd7e9-0548-41bf-9ff1-f45130e4def6n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages