Hello, In fact the BIG difference comes from the fact that JMeter with your test case uses PERSISTENT messages while your perfharness Test uses NON PERSISTENT messages.
I made a test on my machine with a local AMQ 5.5.0 server: JMETER : Generate Summary Results = 199630 in 60,1s = 3319,2/s Avg: 0 Min: 0 Max: 695 Err: 0 (0,00%) Perfharness : totalIterations=219579,avgDuration=60,12,maxrateR=3933,03 Note that if I add a setup Thread Group that runs one sample (to warm up ) (which is what is done by Perfharness I think), I get : Generate Summary Results = 210270 in 60,6s = 3469,2/s Avg: 0 Min: 0 Max: 841 Err: 0 (0,00%) I think documentation should be clearer about this PERSISTENT settings and we should add a new Option to enable NON PERSISTENT messages Regards Philippe M. http://www.ubik-ingenierie.com On Sun, Feb 26, 2012 at 5:23 PM, Bruno Antunes <[email protected]>wrote: > Reported > https://issues.apache.org/bugzilla/show_bug.cgi?id=52773 > > -- > Bruno Antunes > Software Engineer > > On Sun, Feb 26, 2012 at 1:45 PM, Philippe Mouawad < > [email protected]> wrote: > > > Can you create a Bugzilla and attach your test case ? > > > > Thanks > > Regards > > Philippe > > > > On Sun, Feb 26, 2012 at 2:42 PM, Bruno Antunes > > <[email protected]>wrote: > > > > > Just one correction. Test period was 60 seconds (one minute) > > > > > > regards, > > > -- > > > Bruno Antunes > > > Software Engineer > > > > > > > > > On Fri, Feb 24, 2012 at 6:38 PM, Bruno Antunes > > > <[email protected]>wrote: > > > > > > > I have performed a very simple test, using JMS Publisher sampler on > > > > JMeter, and a "jms.r11.Sender" test case on Harness , with similar > > test > > > > conditions: > > > > * No ramp-up, only one thread > > > > * same message size (1000 bytes) > > > > * same destination queue > > > > * same duration test period (60 minutes) > > > > * running as fast as possible (no delay between samples) > > > > > > > > From this tests, I observe that Harness generates almost 90% more > > > messages > > > > than JMeter. As such we achieve greater throughput with one thread > in a > > > one > > > > minute test using Harness > > > > > > > > In order to get same throughput for jmeter, we must configure more > > > threads. > > > > > > > > Tested with JMeter 2.6, and IBM Performance Harness for Java Message > > > > Service 1.2 ( > > > > > > > > > > https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=1c020fe8-4efb-4d70-afb7-0f561120c2aa > > > > ) > > > > > > > > Any ideas of why JMeter generates much less load? I have even run > > jmeter > > > > with no gui, and saves results in CSV format. > > > > > > > > -- > > > > Bruno Antunes > > > > Software Engineer > > > > > > > > > > > > > > > -- > > Cordialement. > > Philippe Mouawad. > > > -- Cordialement. Philippe Mouawad.
