On Feb 12, 2008 5:51 AM, Edward Z. Yang <[EMAIL PROTECTED]> wrote: > Hannes Magnusson wrote: > > There has also been some work on configure.php (see > > http://news.php.net/php.doc/969378560). > > Other than that things have been really quiet around here. > > Ok, the work on configure.php sounds really great, but I don't seem to > be getting any of these benefits. Running configure.php hoses my > computer (memory-wise and CPU-wise) when it hits the validation section: > it appears $dom->xinclude() is to blame for the 1.2 GB of memory it's > consuming, and $dom->validate() is to blame for maxing out the CPU.
I don't know how to respond to this, other than "works fine for me [tm]". pb11 (docs.php.net) had serious issues running configure.php in the past - and before the recent changes the box was incapable of running configure.php successfully so we used the old ./configure && make stuff to push out the builds. After the configure.php changes however the script no longer segfaults and takes less then a minute to complete.. It seems very odd that xinclude is causing you any problems as that should be the fastest operation, the issue is the SYSTEM file entities that "include" files and on-the-fly-validation. This is now "fixed" by activating the small nodes allocation optimization in libxml (2.6.21) and moving the xinclude and validation after the initial load of the document. The downfall of this is however if any errors occur the errormsgs can be a bit cryptic so you'll need to pass --enable-xml-details to get fancy errormsgs with filename+linenumber - this process however requires great amount of ram and a decent cpu. -Hannes
