On 5 Feb 2007, at 11:24, Nicholas Clark wrote:
Something I discovered was that processing TAP is slow. Up to about
7 CPUs,
parallelising tests feeding TAP into the master "thread" was a win.
Beyond
that, the process processing the TAP was the bottleneck, and adding
more
CPUs (and more parallel tests) didn't help. I would assume that
from that
point on it would be better to have each test run by slave harness
processes,
which takes the TAP, parses it, and slings (say) Storable objects
across
to the master.
TAPx::Parser is slightly slower too...
--
Andy Armstrong, hexten.net
