jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Mouawad <philippe.moua...@gmail.com>
Subject Re: PERFORMANCE => Changing JMeter defaults to ensure better performances by default
Date Mon, 24 Dec 2012 16:47:06 GMT
I just wrote one :)

http://www.ubik-ingenierie.com/ubikwiki/index.php?title=JMeter_Performance_and_Tuning_Tips

Regards
Philippe

On Monday, December 24, 2012, Shmuel Krakower wrote:

> Hi,
> I agree with changing the defaults, that's the first and easiest pain
> point.
>
> I also agree with the fact that JMeter has bad reputation with those urban
> legends, but this will change over time.
> I think blogging about this may improve and you just gave me an idea for my
> next blogpost... :)
>
> Best,
> Shmuel Krakower.
> www.Beatsoo.org - re-use your jmeter scripts for application performance
> monitoring from worldwide locations for free.
>
>
> On Mon, Dec 24, 2012 at 4:59 PM, Immanuel Hayden
> <immanuel.hayden@gmail.com <javascript:;>>wrote:
>
> > regarding 2: i think it would be better to have some checkbox in the test
> > plan like "disable taxing listeners (View Result Tree, ...)" like we now
> > have eg. with "run thread groups consecutively" as you then don't have to
> > change the test plan between development and actually running which may
> be
> > prone to introducing errors and/or forgetting stuff.
> >
> >
> > On Mon, Dec 24, 2012 at 2:20 PM, Philippe Mouawad <
> > philippe.mouawad@gmail.com <javascript:;>> wrote:
> >
> > > Hello,
> > >
> > > I am kind of annoyed of reading articles, blogs that say JMeter cannot
> > > perform high Load Tests, consumes lot of memory, generates OutOfMemory
> > ...
> > >
> > > This has become a kind of "Urban Legend" partly due:
> > > - to issues that have been fixed for a while now
> > > - and partly In my opinion to some default configuration parameters
> that
> > > lead to these issues
> > >
> > > In my opinion, we should:
> > >
> > > 1) change these defaults to avoid new comers, beginners fall into all
> > these
> > > traps and others check they are using it well:
> > >
> > >    - Save Service using XML output => Change to CSV
> > >    - Distributed Mode that uses the Standard which is far from being
> the
> > >    best performing Sample Sender => Change to Batch or StrippedBatch
> > >
> > > 2) Add warnings on GUIs of all elements that are more suited during
> > > Scripting than during Load Test :
> > >
> > >    - View Result Tree (I keep seeing people use this element during
> High
> > >    Load Test ! )
> > >    - View Results in Table
> > >    - Graph Results
> > >    - ...
> > >
> > > 3) Add a popup warning when Start and Remote Start are clicked from GUI
> > to
> > > encourage NON GUI mode use (we could add a checkbox Remind Me later
> which
> > > could be unchecked to avoid it again, but at least user would know
> about
> > > it).
> > >
> > > 4) Finally use some kind of visual indicator (RED background) on some
> > > options that have high impact on performance:
> > >
> > >    - Javascript as scripting language
> > >    - Body (unescaped) in Regular Expression Extractor (*this one is a
> > real
> > >    performance killer !*)
> > >    - Encourage JSR223 Samplers + Groovy  + Caching instead of Beanshell
> > >    - ...
> > >
> > >
> > > Maybe we should post this mail on user mailing list to see what users
> > think
> > > about it.
> > >
> > > --
> > > Regards
> > > Philippe M.
> > >
> >
>


-- 
Cordialement.
Philippe Mouawad.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message