Re: Phpdocumentor memory usage

Hi, Large projects require large amounts of memory to do the complex linking and other useful features. I've never had windows stalled by Apache, but I have had Apache freeze. I have an ancient PIII 500 with Win98SE, so I think there are some problems no one can fix. The main issue for which I have no immediate solution is that to perform linking, a list of every element parsed must be kept in memory as an index to pull links from. Also, caching parsed output to disk would be a tremendous speed slowdown. We're entertaining options for version 2.0 only, as any memory usage change will involve a rewrite of the intermediate parsing stage, but have no definite plans that are appealing. Parsing PhpDocumentor itself generally takes about 70-90 MB of memory during parsing, and depending on the converter, can take up to 800 MB (the PDF converter uses a library that is very memory-intensive). I don't have access to a profiler (loading any debugger on my machine just causes apache to freeze after about 15 minutes, and parsing is 10 times slower), so I can't tell you what exactly is eating up the most memory, but this is an issue that we're aware of. For now, the only solution is to upgrade your system, or find a unix platform to do the parsing, as unix handles memory MUCH better than windows. Greg Limbourg Arnaud wrote:

Hello, I tried to generate the documentation for Xoops 2 RC3. After 30 minutes apache was using 100 Mb of memory. I had to reboot, wondows would not let me kill the process. Anybody aware of memory usage issues ?