Tesseract uses very little memory. The most optimal way of using multiple cores is simply to have multiple processes running simultaneously, processing different pages. If you want to get more sophisticated than that, you will have to wait for the completion of the thread-safety project, as tesseract uses lots of globals, and it is currently unsafe to run multiple threads in a single process.Ray.
On Thu, Jan 8, 2009 at 8:34 AM, robert.waters <[email protected]>wrote: > > It seems that tesseract prefers a specific core, like most modern (pre- > parallel) applications. > What is the best method you've found to have tesseract utilize a > multicore machine optimally? > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
