Re: configure optimisations

["Eddie Bell" <ejlbell () gmail com>]

The size is the easiest thing to optimise as a small change in
'configure.ac' translates to a large saving in 'configure'.

As for the time, it is at the very least faster :) My  measurements
varied greatly. They could have been effected by background processes,
hardware etc.

There are some tests which take a long time to run (such as command
line argument limit), removing these from 3rd party scripts should
improve the speed.

thanks for testing
 - eddie

On 19/07/07, Kris Katterjohn <katterjohn () gmail com> wrote:
> Eddie Bell wrote:
> > I've committed some initial changes to the 'configure' system. So far
> > nbase, nsock and nmap have been modified although there is still scope
> > for improvement in the other sections.
> >
> > The changes save around 3800 lines of configure code (130k of disk
> > space) and anywhere between 5 and 15 seconds in run-time. The exact
> > time saved varies but it is always faster
> >
> > I've tried to make the files smaller, faster and simpler by doing the following:
> >
> >    * using 'ifnames' to remove unused macros and tests
> >    * simplifying tests that are only partially used
> >    * reducing redundancy
> >
> > The changes 'should' not break anything but I don't have access to
> > some of the more exotic unix's
> >
> > thanks
> >  - eddie
>
> I just tested it on my Ubuntu box.  I only got an average savings of
> about 2 seconds using the new configures, but if you saved that much
> disk space and you've had up to 15 seconds saved before, then that's
> great!  I didn't have any problems with it.
>
> Thanks,
> Kris Katterjohn

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org