Make the build system non-recursive about eudev HOT 6 CLOSED

1. Their snide remarks mean nothing. Yawn.

2. If the recursion is bad on a multicore then that's a convincing argument. Let me do a test on a 16 core box and see if it really blocks parallelization.

3. As I stated earlier, now that the pieces have settled it make sense to return to non-recursion. However, we may still keep test recursive since it makes little difference, but I'll see as I hack away at it.

from eudev.

Okay for the records. Current build system on 16 core HP 385 G7 proliant 64GB memory, 2.3 GHz.

autogen
real 0m20.291s
user 0m17.427s
sys 0m1.833s

configure
real 0m24.303s
user 0m13.047s
sys 0m10.091s

make -j17
real 0m21.618s
user 0m46.224s
sys 0m6.680s

from eudev.

Okay with commit 8e75277 in the non-recursive branch, we get

autogen
real 0m18.003s
user 0m15.176s
sys 0m1.817s

configure
real 0m23.160s
user 0m12.601s
sys 0m9.277s

make -j17 on 16 core
real 0m9.348s
user 0m38.232s
sys 0m5.813s

Some people will look at this and say "big savings!" I look at it and see, lots of loss in flexibility fro just a few seconds. Note: I have only make the build non-recursive in /src. I can make the whole system non-recursive, but I really want to discuss this as a team before we go in this direction.

from eudev.

FYI that benchmark was for 8e75277 but follow non-recursive branch for the lastest, because there are still some buggies in there.

from eudev.

Looks nice enough for me. Thank you for testing.
On Feb 4, 2013 12:40 AM, "blueness" [email protected] wrote:

FYI that benchmark was for 8e752778e75277but follow non-recursive branch for the lastest, because there are still
some buggies in there.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/43#issuecomment-13058084.

from eudev.

Moving past this issue ...

from eudev.