Revision history [back]

Hey Everyone,

I'm using OpenCV 3.3.0 on an Ubuntu 16.04 VM that I've allocated 8 "cpus" to. My application is tracking an object and interestingly, when I compile opencv with the TBB option set from CMake, the performance is significantly faster than pthreads. With TBB, the application requires 23 seconds to run, compared to 40.5 seconds when using pthreads. The only heavyweight operation in this application is the tracker updating, and I'm currently using the MIL tracker. Does anyone have any ideas? To me, this seems like a bug in OpenCV.

Hey Everyone,

I'm using OpenCV 3.3.0 on an Ubuntu 16.04 VM that I've allocated 8 "cpus" to. My application is tracking an object and interestingly, when I compile opencv with the TBB option set from CMake, the performance is significantly faster than pthreads. With TBB, the application requires 23 seconds to run, compared to 40.5 seconds when using pthreads. When I wrap the tracker->update function with time reads, it's nearly twice as slow when using pthreads. The only heavyweight operation in this application is the tracker updating, and I'm currently using the MIL tracker. Does anyone have any ideas? To me, this seems like a bug in OpenCV.

Hey Everyone,

I'm using OpenCV 3.3.0 on an Ubuntu 16.04 VM that I've allocated 8 "cpus" to. My application is tracking an object and interestingly, when I compile opencv with the TBB option set from CMake, the performance is significantly faster than pthreads. With TBB, the application requires 23 seconds to run, compared to 40.5 seconds when using pthreads. When I wrap the tracker->update function with time reads, it's nearly twice as slow when using pthreads. The only heavyweight operation in this application is the tracker updating, and I'm currently using the MIL tracker. Does anyone have any ideas? To me, this seems like a bug in OpenCV.