Thread: [Doxygen-users] Doxygen Speed Issues

Brought to you by: dimitri

doxygen-users

[Doxygen-users] Doxygen Speed Issues

From: martin s. <mse...@gm...> - 2005-10-27 01:19:33

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?

Re: [Doxygen-users] Doxygen Speed Issues

From: Braden M. <br...@en...> - 2005-10-27 05:08:49

On Wed, 2005-10-26 at 21:19 -0400, martin sweitzer wrote:
> Are there any tips / suggestions / parameters to use to speed up
> doxygen's generation of documentation?  :-)

Make sure you aren't doing this:

        <http://sourceforge.net/mailarchive/message.php?msg_id=11873587>

-- 
Braden McDaniel                           e-mail: <br...@en...>
<http://endoframe.com>                    Jabber: <br...@ja...>

RE: [Doxygen-users] Doxygen Speed Issues

From: Michael M. <Mic...@tt...> - 2005-10-27 11:37:18

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.

 

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?

Re: [Doxygen-users] Doxygen Speed Issues

From: Mike W. <mik...@gl...> - 2005-10-28 14:16:33

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.

> 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
-- 
Three may keep a secret, if two of them are dead.

Re: [Doxygen-users] Doxygen Speed Issues

From: Mike W. <mik...@gl...> - 2005-10-28 14:44:16

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!

RE: [Doxygen-users] Doxygen Speed Issues

From: Michael M. <Mic...@tt...> - 2005-10-28 14:58:45

Hi Mike,

Sadly for me, I've always configured SHOW_DIRECTORIES = NO.  It's also
noticeable that with SEARCH_INCLUDES = NO the output when parsing files
flies along compared to when it is YES.

I really need to make some test cases and dig into the Doxygen source to
work out why though...

Regards,

Mike

> -----Original Message-----
> From: Mike Williams [mailto:mik...@gl...]
> Sent: 28 October 2005 15:44
> To: mik...@gl...
> Cc: Michael McTernan; 'martin sweitzer'; doxygen-
> us...@li...
> Subject: Re: [Doxygen-users] Doxygen Speed Issues
> 
> 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!

Re: [Doxygen-users] Doxygen Speed Issues

From: Braden M. <br...@en...> - 2005-10-28 15:19:50

On Fri, 2005-10-28 at 15:43 +0100, Mike Williams wrote:

> 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!

An easier way to do that is

        $ doxygen -u configfile

-- 
Braden McDaniel                           e-mail: <br...@en...>
<http://endoframe.com>                    Jabber: <br...@ja...>

Re: [Doxygen-users] Doxygen Speed Issues

From: Mike W. <mik...@gl...> - 2005-10-28 16:36:42

Braden McDaniel did utter on 28/10/2005 16:19:
> On Fri, 2005-10-28 at 15:43 +0100, Mike Williams wrote:
> 
> 
>>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!
> 
> 
> An easier way to do that is
> 
>         $ doxygen -u configfile

Still need to do a diff to see what has been updated  :)   I know, could 
go through the release changelog, but these can be buried in the 
plethora of other changes.

TTFN

Mike
-- 
No amateur crastinator am I.

Re: [Doxygen-users] Doxygen Speed Issues

From: Neil W. <li...@co...> - 2005-10-28 22:01:27

On Friday 28 October 2005 5:35 pm, Mike Williams wrote:
> Braden McDaniel did utter on 28/10/2005 16:19:
> > On Fri, 2005-10-28 at 15:43 +0100, Mike Williams wrote:
> >>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!
> >
> > An easier way to do that is
> >
> >         $ doxygen -u configfile
>
> Still need to do a diff to see what has been updated

Check the directory, there should be a configfile.bak

On testing the new options, I found a problem with CREATE_SUBDIRS=20

HTML files in the new subdirectories can't find tabs.css

<link href=3D"../../doxygen.css" rel=3D"stylesheet" type=3D"text/css">
<link href=3D"tabs.css" rel=3D"stylesheet" type=3D"text/css">

Changing this to:
<link href=3D"../../doxygen.css" rel=3D"stylesheet" type=3D"text/css">
<link href=3D"../../tabs.css" rel=3D"stylesheet" type=3D"text/css">

fixes the problem on a per-file basis but I'd rather not have to add a perl=
 /=20
sed script to do that. :-)

On the upside, CREATE_SUBDIRS does ease the I/O burden on my system and avo=
ids=20
locking up in other applications.

=2D-=20

Neil Williams
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/

[Doxygen-users] Any way to hide the "File List"?

From: Philip S. <phi...@gm...> - 2006-03-22 23:05:07

Is there any way to not show the "File List" in the tree view?  (We
distribute the API as compiled DLLs, so the names of the header files isn't
relevant to our users.)

I'm using:

SHOW_USED_FILES        = NO
SOURCE_BROWSER         = NO

but it still shows up.

I'm probably missing something obvious.

	Thanks,
	   Philip.

Re: [Doxygen-users] Any way to hide the "File List"?

From: Jack C. <eha...@gm...> - 2006-03-22 23:47:35

Does SOURCE_BROWSER         =3D NO disable XREFS as well for you?

On 3/22/06, Philip Sharman <phi...@gm...> wrote:
>
> Is there any way to not show the "File List" in the tree view?  (We
> distribute the API as compiled DLLs, so the names of the header files
> isn't
> relevant to our users.)
>
> I'm using:
>
> SHOW_USED_FILES        =3D NO
> SOURCE_BROWSER         =3D NO
>
> but it still shows up.
>
> I'm probably missing something obvious.
>
>        Thanks,
>           Philip.
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=
=3D121642
> _______________________________________________
> Doxygen-users mailing list
> Dox...@li...
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>