Re: [Doxygen-users] Doxygen Speed Issues

[Mike W. <mik...@gl...>]

Mike Williams did utter on 28/10/2005 15:16:
> Michael McTernan did utter on 27/10/2005 12:36:
> 
>> Hi,
>>
>> I found that preprocessing can be really slow and may use much more 
>> memory.
>> In particular the project I was building uses a lot of #includes, and I
>> think that a number of these files contain documentation in them.  
>> It's just
>> my suspicion, but I wondered if Doxygen was parsing the documentation 
>> in the
>> #includes multiple times as each C input file tended to #include the same
>> header files - I need more investigation to be sure.
>>
>>  
>>
>> Still, setting SEARCH_INCLUDES = NO made a big difference.  With it 
>> set to
>> NO, the documentation takes ~40 minutes to build.  With it set to YES,
>> Doxygen ran for 8 hours before exhausting memory and stopping.
> 
> 
> I tried first setting SEARCH_INCLUDES to NO and then removing *.h from 
> the set of input files.  Either change significantly reduced the time 
> taken but at the expense of documentation produced.
> 
> When processing a reasonably large C project the point that seems to 
> take the vast majority of time is when Doxygen says 'Computing 
> dependencies between directories...'
> 
> Currently we generate documentation as part of an overnight build since 
> the time taken is longer than the compilation and linking - and we don't 
> run it over the whole product yet.

Ok, stumbled upon SHOW_DIRECTORIES - setting this to NO reduces 
generation time by two thirds.  The config file is relatively historic, 
so I did a diff with a clean one generated by doxygen and found a bunch 
of new parameters - yay!

>> Regards,
>>
>>  
>>
>> Mike
>>
>>  
>>
>>   _____ 
>> From: dox...@li...
>> [mailto:dox...@li...] On Behalf Of martin
>> sweitzer
>> Sent: 27 October 2005 02:19
>> To: dox...@li...
>> Subject: [Doxygen-users] Doxygen Speed Issues
>>
>>  
>>
>> Are there any tips / suggestions / parameters to use to speed up 
>> doxygen's
>> generation of documentation?  :-)
>>
>> Currently, it takes around 35 minutes to generate the documentation 
>> for our
>> codebase.  It takes around 10 minutes to compile it.
>>
>> Is there an incremental build type funtionality?
>>
> 
> Mike

Mike
-- 
All the world's a stage... and I got third row seats!