This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Why some tests took exorbitant time?

Tags: None
(comma "," separated)
FMD
Registered Member
Posts
25
Karma
0
Hi,

It seems to me, that two of the tests in the test-suite took extraordinary long time especially on my machine.
These are product_large with about 120s and lu with about 180s.

At no time, I've found such long timings by my "cdash-competitors".
Not in the near past, nor months ago. Beside these two tests, no other test is "off the field".

What may the reason(s) for this?

Regards
Frank

P.S.
One of my old and unsolved queries is: How can i submit some special compiler flags (in)to the test suite, like "-Ox" ?
User avatar
bjacob
Registered Member
Posts
658
Karma
3
Tests take long to compile because we try to test as many different things as possible, and since this is a pure template library, every different operation we try means for the compiler more types to instantiate. To make things worse, we try many different matrix types.

Regarding compiler options, you can always edit tests/CMakeLists.txt, scroll down to where we do many ei_add_test's, you'll see that the 2nd parameter allows you to pass compiler options, and some already have.


Join us on Eigen's IRC channel: #eigen on irc.freenode.net
Have a serious interest in Eigen? Then join the mailing list!
FMD
Registered Member
Posts
25
Karma
0
I)
Thank you, I will take a look into cmakelists.txt

II)
Ehm.. I have to rephrase my question:
...extraordinary long run time... product_large.exe 120s, lu.exe 180s, why?
What I am puzzled with, is that other people do record run times (not compile times) in an order of magnitude better for this two particular tests and the rest of the test suite is more or less in par. That is what i have called "extraordinary", not a long time per se.

So, I'm intersected in possible reasons for that phenomenon.
User avatar
bjacob
Registered Member
Posts
658
Karma
3
Ah, ok. So the thing is that the two tests that you mention are so heavy (runtime-wise) that we enable (in the cmakelists) optimization flags (-O2) for them, so that they don't take too long to run. It seems that for some reason these optimization flags get overridden for you.


Join us on Eigen's IRC channel: #eigen on irc.freenode.net
Have a serious interest in Eigen? Then join the mailing list!
Hauke
Registered Member
Posts
109
Karma
3
OS
FMD, please take a look at the CMakeCache.txt file of those builds.

Could it be that CMAKE_BUILD_TYPE:STRING=Debug ?

That just happened to me today! The issue is that on Windows in debug mode the optimization flag Benoit talked about is completely disabled. I have not yet any clue why ctest is per default running in Debug but I have a patch which I could submit.

- Hauke


Bookmarks



Who is online

Registered users: Bing [Bot], daret, Google [Bot], sandyvee, Sogou [Bot]