Mailing-List: contact dev-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jmeter.apache.org
Received-SPF: pass (athena.apache.org: domain of philippe.mouawad@gmail.com
 designates 209.85.223.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAHnoMfoVCKV9K7sLwR05jowF+2qtf2pFNtkUQRRnMyD3aZ1CpA@mail.gmail.com>
References: 
 <CAH9fUpb9XET=p3S6-0Px2us9N0BAVEhSUw6S2oqfevAPB3O6Xw@mail.gmail.com>
	<CAOGo0VZ4onsTmnKSisheUFgqgzofysXKS3MbhGUQW5GpANukKg@mail.gmail.com>
	<CAH9fUpbR7uRFdBLTVj6-2sKJnuS9haNkP2DnbCBfvpRwpj8mfw@mail.gmail.com>
	<CAH9fUpZZrhoaf9Xd_J==m02vneTMj0yX2CCL6yv4J_4iyiry9w@mail.gmail.com>
	<CAOGo0VYeeYQt9zTwPdBNVovpsVrZnBFkE6kzAyrzkBoFU3680A@mail.gmail.com>
	<CAH9fUpafdH2Z63XcC9o_qAC6i7ESXysvzJuYYr7TdqS94+-s4Q@mail.gmail.com>
	<CAOGo0Vaty8Y5PK1h2crAytU=1dA5aDY6=YDn=Bw-VxqnmNzWKA@mail.gmail.com>
	<CAHnoMfoVCKV9K7sLwR05jowF+2qtf2pFNtkUQRRnMyD3aZ1CpA@mail.gmail.com>
Date: Wed, 3 Jul 2013 08:23:15 +0200
Message-ID: 
 <CAH9fUpaTpd+c4z8rHv0kKktH01TwwxTg4xTxawf1+3724Qg3Hg@mail.gmail.com>
Subject: Re: Groovy
From: Philippe Mouawad <philippe.mouawad@gmail.com>
To: "dev@jmeter.apache.org" <dev@jmeter.apache.org>
Content-Type: multipart/alternative; boundary=047d7bdc123839857b04e0957fb2

--047d7bdc123839857b04e0957fb2
Content-Type: text/plain; charset=ISO-8859-1

In my experience Scripting elements are more than intended for prototyping .
In my 10 last recent scripting experience I have used them at least once. I
have met plenty of cases where you absolutely need them ( or you need to
setup an eclipse project with jmeter dependencies to finally generate a
jar, I am sure plenty of testers wouldn't do it).
I also feel it is one of JMeter best feature and gives it a real
flexibility.

With compilable they have nearly as good performance as if a jar had been
created with java classes.

For the argument about having more jars in classpath, the perf loss is
really very tiny and most of it at startup and on class load.
And I feel it goes against reusing in that case.

As for beanshell, ok but I think it will take some time before having the
level of features that groovy has.

Regards
Philippe

On Wednesday, July 3, 2013, Shmuel Krakower wrote:

> Maybe scripting elements are intended for prototyping but from my
> experience I endup using few with most of the test plans I create, as I
> always miss some specific functionality, which can be answered by those
> script elements.
>
> Btw - what was the need when it was decided to add bean shell jars to
> jmeter?
>
> I am not for adding groovy or against.
> On Jul 3, 2013 1:49 AM, "sebb" <sebbaz@gmail.com <javascript:;>> wrote:
>
> > On 2 July 2013 23:26, Philippe Mouawad <philippe.mouawad@gmail.com<javascript:;>>
> wrote:
> > > On Wednesday, July 3, 2013, sebb wrote:
> > >
> > >> On 2 July 2013 22:43, Philippe Mouawad <philippe.mouawad@gmail.com<javascript:;>
> > <javascript:;>>
> > >> wrote:
> > >> > hello,
> > >> > so we include it ?
> > >> >
> > >> > It's +1 for me:
> > >> > - faster than beanshell
> > >> > - maintaned and jdk6 syntax can be used
> > >> > - big community
> > >>
> > >> None of the above require it to be bundled with JMeter.
> > >>
> > >> > - embedding it will encourage its usage
> > >>
> > >> Possibly; I'm not convinced it's necessary to include it.
> > >>
> > >> I think we need to be very careful about adding stuff to JMeter just
> > >> because it may be useful to some users. It's all to easy to end up
> > >> with a bloated product that performs poorly.
> > >>
> > >> on the contrary, adding it will encourage groovy usage instead of
> > > beanshell , and this will give better performances.
> >
> > Only for test plans that use scripting, but having more jars in the
> > classpath can have an adverse effect on all tests.
> >
> > Besides, the scripting test elements are primarily intended for
> > prototyping.
> >
> > Furthermore, BeanShell is hopefully joining Apache Commons soon.
> > It may well end up as fast or faster than Groovy.
> >
> > >> > Regards
> > >> > Philippe
> > >> >
> > >> > On Sunday, June 30, 2013, Philippe Mouawad wrote:
> > >> >
> > >> >> Hello Sebb,
> > >> >> It's Apache 2 license
> > >> >> groovy-all.jar is around 6m
> > >> >>
> > >> >> Regards
> > >> >> Philippe
> > >> >> On Sun, Jun 30, 2013 at 3:41 PM, sebb <sebbaz@gmail.com<javascript:;>
> <javascript:;><javascript:_e({},
> > >> 'cvml', 'sebbaz@gmail.com <javascript:;> <javascript:;>');>
> > >> >> > wrote:
> > >> >>
> > >> >>> On 29 June 2013 22:57, Philippe Mouawad <
> philippe.mouawad@gmail.com <javascript:;>
> > <javascript:;><javascript:_e({},
> > >> 'cvml', 'philippe.mouawad@gmail.com <javascript:;><javascript:;>');>>
> > >> >>> wrote:
> > >> >>> > Hello,
> > >> >>> > what about embedding groovy in next release so that it is
> > >> automatically
> > >> >>> > available to JSR223 sampler ?
> > >> >>>
> > >> >>> How big is it?
> > >> >>> What is the license?
> > >> >>>
> > >> >>> >
> > >> >>> >
> > >> >>> > Regards
> > >> >>> > Philippe
> > >> >>> >
> > >> >>> > --
> > >> >>> > Cordialement.
> > >> >>> > Philippe Mouawad.
> > >> >>>
> > >> >>
> > >> >>
> > >> >>
> > >> >> --
> > >> >> Cordialement.
> > >> >> Philippe Mouawad.
> > >> >>
> > >> >>
> > >> >>
> > >> >
> > >> > --
> > >> > Cordialement.
> > >> > Philippe Mouawad.
> > >>
> > >
> > >
> > > --
> > > Cordialement.
> > > Philippe Mouawad.
> >
>


-- 
Cordialement.
Philippe Mouawad.

--047d7bdc123839857b04e0957fb2--