It turns out I'm wrong - it never worked like this. Thinking about it, what I remember doing is copying all the lines from one .jtl file into one and then loading the file in a JMeter listener. Because the listeners look at the timestamps, the ordering of the samples doesn't much matter for a listener like Aggregate Listener.
I still like the idea of just being able to load as many *.jtl files into your listener as you want. Sorry! (*shame*) -Mike On Thu, 2005-06-16 at 09:35 -0400, Michael Stover wrote: > Hmm, well, much to my annoyance, I find it's not possible anymore. It > used to be that one could open multiple .jtl files in a listener and it > would just keep adding the samples in. With the timestamp info, it > would even be able to calculate a merged total throughput (assuming the > results were from simultaneous runs on machines that agreed on the > time). It was a very handy way to run multiple instances of JMeter in > non-gui mode on multiple machines, and then view the aggregate data > afterward. > > I would like that function back. If one needs a listener cleared, > that's a menu function after all - I see no reason it has to assume you > want it cleared when loading a new file. > > -Mike > > On Thu, 2005-06-16 at 13:44 +0300, Yuval wrote: > > Hi Mike, > > > > How can merge the results from multiple test runs via JMeter? > > > > Thanks, > > > > Y. > > > > On 6/15/05, Michael Stover <[EMAIL PROTECTED]> wrote: > > > > > > You can merge results from multiple test runs - actually, JMeter will do > > > it for you in the listeners. > > > > > > Bandwidth/IO is absolutely an issue when the client is receiving full > > > requests from multiple remote servers. Probably I should just say "IO". > > > Bandwidth makes people think only of the pipe, not the client machines > > > ability to read and process all those bytes. > > > > > > You had mentioned 500 threads only used 35% of cpu and 25% of memory, so > > > I'm not sure why 1000 is suddenly killing your machine. java 1.4 and > > > 1.5 can deal with 1000 threads, given the hardware resources. Have you > > > bumped up the jvm heap size sufficiently? > > > > > > You can run multiple instances on the same machine, but I don't expect > > > things to work better that way. More likely, it's just a way to use > > > more memory. > > > > > > -Mike > > > > > > On Wed, 2005-06-15 at 17:06 +0300, Yuval wrote: > > > > Hi Mike, > > > > But I want to run load test which will include few jmeter-servers, and > > > if > > > > possible, to enjoy the benefit of seeing all the results from one place. > > > > I'm not sure it's a bandwidth issue. When I define 1000 threads in the > > > > thread group, the jmeter-server stops working after few minutes - when I > > > > only have 30-40 working threads. > > > > Don't you think that it may be that there are too many threads for this > > > > process? > > > > Is it possible to run 2 jmeter servers on the same machine, listening on > > > > different ports? > > > > Thanks, > > > > Y. > > > > > > > > On 6/15/05, Michael Stover <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Most likely the problem is bandwidth/IO. The server is forwarding > > > every > > > > > request to the client JMeter machine. That means the server's IO is > > > > > doing double duty - receiving all those requests and turning around > > > and > > > > > sending them all out. If you tried running your test in normal non-gui > > > > > mode on the solaris, and then import the resulting .jtl file afterward > > > > > to your gui client, see if that doesn't increase your bounds. > > > > > > > > > > Because JMeter's remoting abilities does nothing to relieve bandwidth > > > > > limits, I don't use it - it's not actually a useful way currently to > > > > > scale load testing up. Better is to simply run multiple non-gui > > > > > instances on multiple machines. > > > > > > > > > > -Mike > > > > > > > > > > On Wed, 2005-06-15 at 10:42 +0300, Yuval wrote: > > > > > > Hi, > > > > > > I'm trying to run a load test (web) with the jmeter server running > > > on a > > > > > > Solaris machine. > > > > > > The problem is that it seems like I can run only ~500 users, while > > > the > > > > > CPU > > > > > > is only around 35% and the memory is on 25%. > > > > > > Anyone knows if there's a limitation of the max number of threads > > > per > > > > > > process on Solaris, or any other cause for this issue? > > > > > > Thanks, > > > > > > Y. > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
