DoubangoTelecom
commented
4 years ago Call the Init function once at server startup.
You have to protect the process function to avoid concurrent access:
mutex.lock();
process();
mutex.unlock();The process function is already massively multithreaded. Without access control you'll be forking the threads and will end up flooding your CPU. On quad core with hyper-threading you'll have 8 threads created by the SDK. If you're using 8 threads to call the process function then, you'll have 8x8=64 threads. Our code is already well designed to avoid context switching and thread forking (https://github.com/DoubangoTelecom/compv/tree/master/base/parallel). See https://www.doubango.org/SDKs/mrz/docs/Architecture_overview.html#thread-safety.
The minimum frame rate is 15fps (https://github.com/DoubangoTelecom/ultimateMRZ-SDK/tree/master/samples/c%2B%2B/benchmark#peformance-numbers) which means you could process at least 900 requests per minutes when all images have MRZ lines.
imranbaloch
Just need to confirm the sample code in your repo will be enough to handle the normal sever load (at least 100 Requests per Minute) or there are some threading issues we need to tackle,
There will be a lot of threads that will be executing the same code parallelly. off course,
somPostedFileToWebServerwill be different for each request.