On Oct 30, 2007, at 5:16 PM, Peter Laurens wrote:

>
>> ... you should take a look at
>> the GC core module.
>
> Thanks - I disabled the GC for the duration of the system() task (the
> JMeter invocation). The issue remained, so I can discount Ruby's GC as
> the culprit. My current thinking is leaning to some kind of threads
> issue, perhaps also something to do with OS X thread limits.
> -

Kernel.system forks and execs a new process for the command (via the
C library version of system()) so I don't see how threads in the
jmeter process could be affected at all by anything Ruby is doing.
In fact Ruby isn't really 'doing' anything other then waiting for
the child process to complete.