Is your tesseract DLL built with single threaded execution? Hopefully it is.
Background:
Charles Weld's build of tesseract DLL configures the DLL build for multi-threading of image processing (leptonica), etc. This makes it run slower on servers with multiple CPUs because of core affinity (also called processor affinity).
In our case, we have multiple threads of the C# engine instances and if each engine instance also uses multi-threading (like above) then it leads to lower performance on servers/VMs due to core affinity.
Is your tesseract DLL built with single threaded execution? Hopefully it is. Background: Charles Weld's build of tesseract DLL configures the DLL build for multi-threading of image processing (leptonica), etc. This makes it run slower on servers with multiple CPUs because of core affinity (also called processor affinity). In our case, we have multiple threads of the C# engine instances and if each engine instance also uses multi-threading (like above) then it leads to lower performance on servers/VMs due to core affinity.
Thank you.