Memory consumption

Hi list,


today I played with phpdocu.
Unfortunatly I had to find out that the memory consumption
when creating
documentation for a larger project is beyond any acceptable
borders.

In this case I fired phpdocu on a TYPO3 installation
(basically the core
with just some tiny extensions). Even after raising the
cli-php-memory_limit to 1GB (!) the project ended after
scanning about
1/3 of source files with a memory-exhausted message.
This should IMHO be considered as a critical bug, because it
renders
this project useless for real-world usage, if memory usage
scales
something like linear with the number of input files. Most
webhoster
will probably limit php to something around 64MB, so this
should be the
limit for this project.

Are there any hacks I could apply to make phpdocu run over
some bigger
code-basis like TYPO3 or horde?
Is it possible to split scanning and merge them in a final
run?
Are there plans to fix this issue?
What about max_execution_time and other limits? One might
probably run
into problems like this also.

It would be nice if there would be a solution to this, at
least in the
long run. All in all this project looks nice and I would
like to stick
with it.


Greetings
Christian

------------------------------------------------------------
-------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and
a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Phpdocu-general mailing list
Phpdocu-generallists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/phpdocu
-general