[Dune] dunecontrol not faster with set DUNE_CONTROL_PATH

Christian Engwer christian.engwer at uni-muenster.de
Wed May 23 17:42:34 CEST 2012


Hi Christoph,

On Wed, May 23, 2012 at 04:40:59PM +0200, Christoph Grüninger wrote:
> Hi Christian and Markus,
> I wrote an additional section for the buildsystem documentation and
> finally tested what I wrote. I encountered the same problem as
> Markus, no speedup.
> Is this feature maybe broken? 

Why broken? The feature does work, perhaps you misinterpreted a
sideeffect for a feature. The difference in the timeings is merely due
to measuring differences.

If you want to optimize something, you should always have a look at
teh timings of the different components and by far the most
timeconsuming part in dunecontrol is the recursive algorithm for the
construction of the dependency tree.

Also you would get different timings, if your home is stored on a slow
nfs-volume, or if you search a large home instead of just the dune
directory.

Christian

> At least the value of the environment
> variable is honored because if I place an empty dune.module file in
> a sub-sub-directory it is only found without the opts file.
> 
> >time ./dune-common/bin/dunecontrol --opts=debug.opts
> --- going to build dune-common dune-geometry dune-grid
> dune-localfunctions dune-istl dumux dune-pdelab dune-multidomaingrid
> dune-multidomain dumux-devel dumux-lecture dune-grid-howto
> dune-pdelab-howto duneweb  ---
> --- done ---
> 
> real    0m6.955s
> user    0m1.240s
> sys     0m1.708s
> >time ./dune-common/bin/dunecontrol
> --- going to build dune-common dune-geometry dune-grid
> dune-multidomaingrid dune-localfunctions dune-istl dumux dune-pdelab
> dune-multidomain dumux-devel duneweb dune-grid-howto dumux-lecture
> dune-pdelab-howto  ---
> --- done ---
> 
> real    0m6.860s
> user    0m1.267s
> sys     0m1.677s
> >time ./dune-common/bin/dunecontrol --opts=debug.opts
> --- going to build dune-common dune-geometry dune-grid
> dune-localfunctions dune-istl dumux dune-pdelab dune-multidomaingrid
> dune-multidomain dumux-devel dumux-lecture dune-grid-howto
> dune-pdelab-howto duneweb  ---
> --- done ---
> 
> real    0m6.850s
> user    0m1.235s
> sys     0m1.622s
> >time ls */dune.module | tr '\n' ':'
> dumux-devel/dune.module:dumux/dune.module:dumux-lecture/dune.module:dune-common/dune.module:dune-geometry/dune.module:dune-grid/dune.module:dune-grid-howto/dune.module:dune-istl/dune.module:dune-localfunctions/dune.module:dune-multidomain/dune.module:dune-multidomaingrid/dune.module:dune-pdelab/dune.module:dune-pdelab-howto/dune.module:dune-web/dune.module:
> real    0m0.003s
> user    0m0.001s
> sys     0m0.003s
> 
> Bye
> Christoph
> 
> Am 23.05.2012 11:37, schrieb Dune:
> >THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
> >
> >The following task has a new comment added:
> >
> >FS#1118 - find command in dunemodule.lib should get some extra options.
> >User who did this - Markus Blatt (mblatt)
> >
> >----------
> >Speaking of time savings:
> >
> >On my system I have 25 modules in the directory. Without setting the
> >DUNE_CONTROL_PATH "./dune-common/bin/dunecontrol --print" takes 9.47
> >seconds.
> >If I set the control path with DUNE_CONTROL_PATH=(find . -name
> >dune.module|tr 'n' ':') it even takes 9,60 seconds (weired)
> >----------
> >
> >More information can be found at the following URL:
> >http://www.dune-project.org/flyspray/index.php?do=details&task_id=1118#comment3620
> 
> 
> -- 
> People who are more than casually interested in computers should have
> at least some idea of what the underlying hardware is like. Otherwise
> the programs they write will be pretty weird.         -- Donald Knuth
> 
> _______________________________________________
> Dune mailing list
> Dune at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune
> 



More information about the Dune mailing list