|Message: Re: superslow make on a cluster over the network||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
On Thu, 05 Nov 2009 01:34:49 GMT, Valery Taranenko wrote: > i'm not familiar with intricate g4 make system, but if i look into the > user code intermediate make-process files in > $G4WORKDIR/tmp/Linux/usercode I see those dependency .d files where all > header files of g4 as well as the OS(!) are listed. some of those files > hold 500 or even 800 dependencies. now, imagine, how make build those. > it must be opening each source or header file, parsing for includes, > open those includes and so on and so on. one poor g4 user code analysis > file has 500 dependencies--pretty crazy. this sounds like an overkill. > the bottleneck must be I/O on the disk system when make process > constantly opens hundreds of those files while building dependencies.
O.k., if your filesystem is completely remote (i.e. even the system parts are network mounted) then I can see why there would be a problem here. However, I don't think the number of dependencies you're seeing is completely crazy. Even Automake/CMake will generate similar sized ".d" files - I've certainly seen this even in non-Geant4 pure C++ projects.
I'm not aware of any improvement that can be made here (doesn't mean there isn't one though)- as you've found it's the remote filesystem that's the cause of the problem. Once you've done the initial big build, the future incremental changes should run faster.