shadowsheep's profile - activity

@matman: Yep! It works!

    Hello, World! 3.0.0
 STD SOBEL STARTED 1ST CALL

 STD SOBEL FINISHED 1ST CALL in 20.2502, total 39.5455
 STD SOBEL STARTED 2ND CALL

 STD SOBEL FINISHED 2ND CALL in 20.683, total 67.209

So @matman if you wanna answer this question, I'll mark it like "solved" because in fact it solves it! Thanks to all.

Perhaps that's strange, it's like OpenCV 3.0 setup OpenCL driver (like GPU module) even if I don't ask them to use it.

Thank you all and see you at the next question.

@Eduardo, thanks to have given it a try. So, like StevenPuttemans says, it seems like OpenCV 3.0 have a first function call overhead.

I've so made a new test with only two calls that seems to enforce that assumption.

I've put the code in the question.

Hello, World! 2.4.9

STD SOBEL STARTED 1ST CALL

STD SOBEL FINISHED 1ST CALL in 22.2636, total 45.8063 STD SOBEL STARTED 2ND CALL

STD SOBEL FINISHED 2ND CALL in 23.4234, total 86.663

Hello, World! 3.0.0

STD SOBEL STARTED 1ST CALL

STD SOBEL FINISHED 1ST CALL in 426.064, total 438.489 STD SOBEL STARTED 2ND CALL

STD SOBEL FINISHED 2ND CALL in 22.0421, total 469.745

Yep, so if you wanna try the src with the attach image we could check the performance on your system.

There are no pdb files. Only src and dll and lib used :) It's the world300.dll that take the most of the space. Have you looked at the zip?! :/

I've put all the dll I've used right because you could try my dll!

The question is answer by Eduardo when he asked me to try the prebuild binaries. Because the problem I'm experiencing there's also with the prebuild version I've open another question here: http://answers.opencv.org/question/67...

I'm experiencing a very performance differences between 2.4.9 and 3.0.

With the simple Soble function I see OpenCV 3.0 run 10x slower than OpenCV 2.4.9 ... O_O ...

I've build up a Visual Studio 2013 project self contained with my benchmark.

Could anyone try and tell me if It sees the same performance difference and could someone explain me the reason?

The project could be downloaded at: http://www.versionestabile.it/opencv/...

With @Eduardo, @StevenPuttemans we ended up to note that OpenCV 3.0 Sobel First Call has a very big overhead, right near 700msec.

cout << "Hello, World! " << CV_VERSION;

int64 A, B;
A = getTickCount();

string _image_name = "equalizzata300.bmp";
string _image_path = "../img/";
Mat image;
image = imread(_image_path + _image_name, CV_8UC3);

if (!image.data)
{
    cout << "Could not open or find the image" << std::endl;
    return;
}

int scale = 1;
int delta = 0;
int ddepth = CV_16S;

Mat grad;

int64 a, b;

std::cout << "\n STD SOBEL STARTED 1ST CALL \n";
a = getTickCount();
Sobel(image, grad, ddepth, 1, 1, 5, scale, delta, BORDER_DEFAULT);
b = getTickCount();
convertScaleAbs(grad, grad);
B = getTickCount();
cout << "\n STD SOBEL FINISHED 1ST CALL in " << 1000 * (((double)(b - a)) / getTickFrequency()) << ", total " << 1000 * (((double)(B - A)) / getTickFrequency());

std::cout << "\n STD SOBEL STARTED 2ND CALL \n";
a = getTickCount();
Sobel(image, grad, ddepth, 1, 1, 5, scale, delta, BORDER_DEFAULT);
b = getTickCount();
convertScaleAbs(grad, grad);
B = getTickCount();
cout << "\n STD SOBEL FINISHED 2ND CALL in " << 1000 * (((double)(b - a)) / getTickFrequency()) << ", total " << 1000 * (((double)(B - A)) / getTickFrequency());

namedWindow("Sobel", CV_WINDOW_AUTOSIZE);
imshow("Sobel", grad);
waitKey(0);

The question now is: Does someone know the reason of that? Is that true also for other image processing functions?

Yes, the code below

int scale = 1;
int delta = 0;
int ddepth = CV_16S;

Mat grad;

int a, b;

cout << "\n STD SOBEL STARTED \n";
a = getTickCount();
Sobel(image, grad, ddepth, 1, 1, 5, scale, delta, BORDER_DEFAULT);
b = getTickCount();

printf("\n STD SOBEL FINISHED in %f, total = %f \n", 1000 * (((double)(b - a)) / getTickFrequency()), 1000 * (((double)(B - A)) / getTickFrequency()));

Run faster with OpenCV 2.4.9 than OpenCV 3.0

Eduardo I've tried also with the precompiled *world300.dll and I've got the same lower performances than version 2.4.9. But now the question is... why with OpenCV 3.0.0 the sobel performance are so degraded than OpenCV 2.4.9?

I've posted my CMAKE output. Hope it helps us to find the reason...

You are trying to build for x64 architecture? If so, It's because your application try to load the wrong version of dll. To check this, first of all try to copy all the *300.dll in your output dir (for Release) or *300d.dll (for Debug).

Run the .exe program and if now it works, all you have to do is to make a custom build in order to copy the right opencv dll in your outdir at every build. Or you must put on your path the opencv build\bin dir.