I'm also interested in this question. Have you read this issue on the tesseract repository ? https://github.com/tesseract-ocr/tesseract/issues/263
The 2 main things I can read on different issues are custom kernel configuration and single threading. An example of custom kernel configuration : https://make-linux-fast-again.com/) As for the single thread, the tesseract executable can use multithreading to speed up the OCR processing of a single page. The gain is not really large, it costs excessive CPU overhead, and so the suggested solution is to disable that, either at compile time (--disable-openmp) or at run time ( OMP_THREAD_LIMIT=1). You then have to run as much tesseract workers as your core total number. That's my understanding but an expert point of view on the matter would be greatly appreciated. On Wednesday, April 15, 2020 at 9:13:03 PM UTC+2, adamuk73 wrote: > > I'm interested to know how hardware-sensitive Tesseract 4 is to hardware. > For example is double number of cores going to double to processing speed? > Or dual cpu set ups? > > Does Tesseract mostly run in RAM or does it use much hdd? > > Any guidance would be appreciated > . I'm looking to run an instance of Tesseract on a x86 box running Centos. > > Thanks in advance. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-ocr/affc7488-2102-41ac-97c3-e0a25c3089a0%40googlegroups.com.
