Running the same test with double the DPI doubles the memory usage.
--
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-ocr+unsubscr...@googlegroups.com.
I ran a test on tesseract 4 on Centos 8 running around 67 MB of tiff images
(around 260) and the process consistently took just over 100 meg of RAM
though it did take a long time to process. i7-6600U running 2 cores on a
VM with 2 GB of RAM
On Friday, April 17, 2020 at 11:42:25 AM UTC+1, mit
That's really useful, thanks!
--
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-ocr+unsubscr...@googlegroups.com.
To view this discussion on the web
Looks as though Tesseract only uses 4 cores maximum but can be set to run
fewer via setting OMP_THREAD_LIMIT
https://github.com/tesseract-ocr/tesseract/blob/master/doc/tesseract.1.asc
On Wednesday, April 15, 2020 at 8:13:03 PM UTC+1, adamuk73 wrote:
>
> I'm interested to know how ha
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
5 matches
Mail list logo
