Hello Dmitri,
Am Donnerstag, 31. Oktober 2013 09:01:44 UTC+1 schrieb Dmitri Silaev: > Tesseract at this time does not take advantage of multi-processor or > multi-core architecture. A single instance of Tesseract-enabled app > would run on a single core, hence all that matters is the clock, > memory and FSB speed, cache etc. Unless you make your own efforts to > write a multi-threaded Tesseract API based app, chopping an input > image to pieces and processing them in parallel. However special care > and manual changes to Tesseract code are required to make it > thread-safe. > > That is not right. Tesseract can take profit if compiled with gcc enabled autovectorization. The speed difference will be significant (do not remember the exact results of my autovectorization experiments). See http://gcc.gnu.org/projects/tree-ssa/vectorization.html for details how to enable it. With best regards Andreas -- -- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/tesseract-ocr?hl=en --- 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]. For more options, visit https://groups.google.com/groups/opt_out.
