On 2000-01-24, Zeugswetter Andreas SB mentioned:
>
> > > Couldn't we test some of these parameters inside configure and set
> > > them there?
> >
> > If we could figure out a reasonably cheap way of estimating these
> > numbers, it'd be worth setting up custom values at installation time.
>
> Imho this whole idea is not so good. (Sorry)
>
> My points are:
> 1. even if it is good for an optimizer to be smart,
> it is even more important, that it is predictable
ISTM that by the nature of things the most important capability of an
optimizer is to yield optimal results. This, however, does not have to be
mutually exclusive with predictability. If you estimate some CPU and disk
parameters and write them into a config file, then you can always give
this config file to a bug fixer. It will still work on his machine, just
less than optimally.
> 2. I compile on test machine, production is completely different
> (more processors, faster disks and controllers)
You're completely right. This has no place in configure. It will have to
be a separate tool which you can run after building and installing.
--
Peter Eisentraut Sernanders väg 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden
