Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Speedier 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Just out of curiosity, it would be nice to know whether the traditional wisdom of overcommitting by one processor works (that is, is -j3 really faster than -j2), and also how much overovercommitting (-j4) trashes the systems?
    • I was kinda wondering the same thing myself ... but it takes so long to do each build, I don't want to spend the time doing the benchmarks! :-)

      make -j2, G5:

      real    2m11.921s
      user    3m26.660s
      sys     0m45.240s

      make -j3, G5:

      real    2m13.723s
      user    3m29.480s
      sys     0m49.440s

      make -j4, G5:

      real    2m25.240s
      user    3m31.290s
      sys     0m50.420s

      make -j10, G5:

      real    2m24.177s
      user    3

    • Just for the heck of it, on a dual proc Xeon/2.4GHz, also with 2GB RAM:

      make -j3, Xeon:

      real    1m29.770s
      user    3m57.040s
      sys     0m16.460s

      make -j5, Xeon:

      real    1m25.995s
      user    4m59.250s
      sys     0m18.930s

      This machine does "hyper-threading", so it thinks it has four processors even though it has only two, hence the -j5 run. Doesn't seem to make much difference. Anyway, this Xeon compiles perl faster than the G5, by a lot. I don't kn

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.