Why would this be? -> When I reinitialize tesseract for every call in a loop it consistently runs faster by a something like .1 second per loop iteration

[fsbo.c...@gmail.com]

I have a loop that calls SetImage() and GetUTF8Text() once for each iteration of the loop. 

I have found that when I call tesseract::TessBaseAPI *api = new tesseract::TessBaseAPI() and api->End() at the beginning and end of the loop, I actually get about .1 second improvement in time performance than if I only init and end tesseract once. 

Why would this counterintuitive thing happen? Based on these timings I'm assuming the process of clearing the contents of the previous call must be significantly slower than reinitializing tesseract, but this would still be quite counterintuitive.

[fsbo.c...@gmail.com]

To anyone else who may run across this, it is because of the way C++ uses scope to optimize the code when it compiles. Things that are within the scope of the for loop will run faster than things that have larger scope.

[Nick White]

On Fri, Sep 11, 2015 at 12:13:02AM -0700, fsbo.c...@gmail.com wrote:
> To anyone else who may run across this, it is because of the way C++ uses scope
> to optimize the code when it compiles. Things that are within the scope of the
> for loop will run faster than things that have larger scope.

Thanks for the info!