Re: Many slaves or many threads?
Subject Re: Many slaves or many threads?
should stop you from increasing the thread.
subjective, but still very much true).
messes up your transaction response time.
the CPU which reduces CPU queuing. I hope you got my point.
> it - so there is a total limit to the cpu and memory.
> More slaves means more overhead in terms of the machine setup.
> more threads or more slaves?
> 1 thread on 10 slaves?
> > Betreff: RE: Many slaves or many threads?
> > more slaves in the setup.
> > Subject: Re: Many slaves or many threads?
> > machine then even 100 threads might be too taxing for it.
> > threads and introduce more slaves, if no then increase the threads.
> > > slave runs in a virtual machine).
> > > Is this a sensible setup?
> > > Would we be better off running 1 jmeter-slave with 100 threads?
> > > Or 5 slaves with 20 threads?
> > > Or something else?
> > > How does everyone else setup tests that use many threads/processes?