Comments on: Rephlux and PHP memory usage with a PEAR surpise

By: SitePoint Blogs » Simple Test Remote Testing

SitePoint Blogs » Simple Test Remote Testing — Tue, 25 Apr 2006 00:00:03 +0000

[...] For reasons explained by Jeff here, we’ve been looking for ways to run WACT’s test suite in a way that won’t run into PHP’s memory limit and the obvious solution is execute the tests in smaller groups over the network, meaning Apache will create a new child for each group, each child having a fresh chunk of memory to gobble up. [...]

By: bharris

bharris — Mon, 09 Aug 2004 03:36:15 +0000

Jeff…thanks for the ‘memory check hack’. I needed something to make memory usage measurements. Your ‘roll-your-own’ check was very handy indeed.

By: Jimmy

Jimmy — Mon, 28 Jun 2004 16:22:59 +0000

In the CVS it works fine, its just that in the earlier version people were having problems with it.

But either way, nice!

By: Lukas

Lukas — Mon, 21 Jun 2004 15:45:22 +0000

this issue is fixed in CVS

By: Jeff Moore

Jeff Moore — Fri, 28 May 2004 15:39:09 +0000

Very nice, Harry!

By: Harry Fuecks

Harry Fuecks — Fri, 28 May 2004 14:26:59 +0000

HTMLSax 3.0.0 is out and PEAR.php is gone (apart from some lazy includes on errors that WACT will never encounter) – updated WACT for the (slightly modified) API. Best make sure you have the latest.

By: Harry Fuecks

Harry Fuecks — Fri, 28 May 2004 09:01:07 +0000

Nice discovery

Just started sorting out HTMLSax BTW – it’s now under PHP’s CVS here and have already elimated the PEAR dependancy this example – basically my fault for making assumptions about comment syntax – Word generates bizarre stuff like: