Re: [Wireshark-commits] rev 49995: /trunk/ /trunk/: macosx-setup.sh

[Guy Harris <guy () alum mit edu>]

On Jun 18, 2013, at 9:39 AM, Dirk Jagdmann <doj () cubic org> wrote:

> > Very nice indeed! The only thing that should be done outside the script
> > is setting -j 3: On some systems it is too much, on others it is too
> > little. It should be set in the command line, not the script.
>
> I could change it to something like:
>
> if [ -z "$MAKE_BUILD_OPT" ] ; then
>  MAKE_BUILD_OPT="-j 3"
> fi
>
> This way the user can set custom make options, but the script has a default.

How many processor cores does your machine have, and are they multi-threaded?

I have a 4-dual-threaded-core machine (and a solid-state disk and a lot of memory), and "-j 8" seems to run the CPU at 
about 100%.  I don't know whether "number of threads" would be a good default in all cases - what you really want is to 
keep cranking up the number of jobs until things don't get faster, but that's a pain - but, if it is a good default, 
then
 
        sysctl -n hw.logicalcpu

would give cores*threads-per-core (tested on Snow Leopard, Lion, and Mountain Lion; the script doesn't work on Leopard, 
as the versions of at least some of the software won't configure and build, and I gave up trying to make them build).

(I originally used -j 4, but then saw something about a multi-threaded version of the IBM System/360 Model 195 that 
noted that multi-threading can help deal with pipeline bubbles due to unpredicted or mispredicted branches, so I tried 
-j 8 and found the CPU was busier than with -j 4.)
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe