1. If you want to talk about tesseract performance you should get rid of
all that wrappers around (you are wrapping tesseract with python library,
and you put it to python app, then you all that put to webserver...)
2. Next: provide a testing case so others can check your performance
measurements.
Related discussion at https://github.com/tesseract-ocr/tesseract/issues/3109
--
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...@googlegro
Also we wanted without OMP_THREAD_LIMIT=1 is tesseract-4.1 is running multi
threading or not?
On Thu, Oct 1, 2020 at 11:23 AM Sarath C P wrote:
> Hi,
>> Please see steps followed.
>>
>> OS: LINUX, 4 CPUS , 2 CORES
>
>> Version tesseract - 4.1
>>
>> 1. Our python web application running in n
>
> Hi,
> Please see steps followed.
>
> OS: LINUX, 4 CPUS , 2 CORES
> Version tesseract - 4.1
>
> 1. Our python web application running in nginx and gunicorn(3 worker and 1
> thread)
>
> 2. We tried to stimulate 3 requests in parallel using script.
>
> 3. In tesseract - 4.1 (*Openmp disabled
1. OMP_THREAD_LIMIT is an environment variable so it affects "everything"
not only tesseract.
2. How did you measure performance? Provide details including OS, hw etc.
Zdenko
st 30. 9. 2020 o 14:05 Sarath C P napísal(a):
> OpenMP disabled in tesseract-ocr default. but when I am seeting
> OMP_T
OpenMP disabled in tesseract-ocr default. but when I am seeting
OMP_THREAD_LIMIT it gives performance improvement why?
--
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 em
6 matches
Mail list logo
