Re: Re: PEAR 1.4.0a9 fixes memory problems in my tests

On Fri, 25 Mar 2005 10:52:24 -0500, Davey Shafik <davey@php.net> wrote: > Greg, > > This is most excellent to hear, though I could care less (I never had an > issue, 1GB RAM and no memory limits :D) except that it will keep a lot > of people from bitching at you :) > > What did you do that caused the reduction in memory usage? I'm curious, > probably something we all could learn from and help us to reduce memory > usage in all our code (I have been very memory concious in Cerebral > Cortex but never done any profiling or anything) :D > AFAIK he seperated the package.xml reading and writing into seperate classes. But I didn't read all of the commit messages, so I may be totally wrong. ;-) > - Davey > > > Greg Beaver wrote: > > Hello, > > > > For all standard commands, including Web Installer-used commands like > > list-all, list, install/upgrade/upgrade-all and so on, PEAR 1.4.0a9 has > > a significantly lower memory footprint, and clocks in under 8 MB. > > > > Packaging can still take oodles of memory because of the memory hit by > > token_get_all(). This is especially true for packages like PEAR that > > have both a package.xml 1.0 and 2.0, as this puts memory usage at about > > 6 MB prior to source code analysis. However, I am under the impression > > that most devs doing packaging will be doing this on a development > > machine that they control, so unless my impression is wrong, this should > > not be an issue, as the "peardev" command can be used for those who wish > > to keep memory_limit at 8MB in php.ini. > > > > Other important fixes are in this release, particularly for > > installing/upgrading PECL packages. > > > > Now is a good time for those who wish to have input into how things are > > implemented to take a good, hard look at the installer, and try to > > either break it or to use it to solve problems. I am going full-tilt > > into documenting the new features. Once they are documented, it will be > > getting close to the first beta release which means feature freeze. > > Note: the freeze will not happen until it is clear that lots of people > > have tried things and are pretty happy. > > > > Your best friend in this process is going to be: > > > > 1) pear help > > 2) pear help <commandname> like "pear help channel-add" > > 3) the manual at pear.php.net, particularly this section: > > > > > > http://pear.php.net/manual/en/guide.developers.package2.php > > > > Also, the as-yet unpublished changes to > > http://pear.php.net/manual/en/installation.cli.php in > > peardoc/en/chapters/installation.xml which can be seen in my last commit > > in pear-doc archives. > > 4) me > > > > Greg > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Justin Patrin