I'm also interested in this question. Have you read this issue on the tesseract repository ?
The 2 main things I can read on different issues are custom kernel configuration and single threading.
An example of custom kernel configuration :
https://make-linux-fast-again.com/)
As for the single thread, the tesseract executable can use multithreading to speed up the OCR processing of a single page. The gain is not really large, it costs excessive CPU overhead, and so the suggested solution is to disable that, either at compile time (--disable-openmp) or at run time (OMP_THREAD_LIMIT=1). You then have to run as much tesseract workers as your core total number.
That's my understanding but an expert point of view on the matter would be greatly appreciated.