Hi > > with distributed testing): > > > Should i do the same when launching jmeter -s on the remote server. > > > I have numerous traces on the server console too! > > > > I think server is more important, because IT is doing the test. It has to > > have memory for results. > This is not the case - the server sends all results back to the controlling > GUI machine, > which stores and displays the results. The server does not hang onto the > results in memory after passing them.
This is perfectly true! but server also needs memory for temporary sampleresults and creating many strings from it (as I said in previous mail about gcollector). I encountered this problem yesterday = many threads + complicated scenario + fairy long responses + even no logging at all = OutOfMemory error. Increasing -Xmx helped.... regards Michal Kostrzewa -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
