Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "JMeter Users List" <jmeter-user@jakarta.apache.org>
Received-SPF: pass (athena.apache.org: domain of flyingrhenquest@gmail.com
 designates 209.85.161.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1316766791339-4832808.post@n5.nabble.com>
References: <1316719202410-4831233.post@n5.nabble.com>
	<1316761731151-4832617.post@n5.nabble.com>
	<CAEYYuFjhBQr8aUmV+4OPrvv00p5UH3ZN9CFa_YTF84-5rx=dAg@mail.gmail.com>
	<1316766791339-4832808.post@n5.nabble.com>
Date: Fri, 23 Sep 2011 09:12:14 -0600
Message-ID: 
 <CAEYYuFjBDSzcVo9jOV0kpiP4HJN9E10QbYDPJ6uOKi7ogDsm=Q@mail.gmail.com>
Subject: Re: Bean Shell Preprocessor query
From: Bruce Ide <flyingrhenquest@gmail.com>
To: JMeter Users List <jmeter-user@jakarta.apache.org>
Content-Type: multipart/alternative; boundary=00151744109cf8464b04ad9d3b4e

--00151744109cf8464b04ad9d3b4e
Content-Type: text/plain; charset=ISO-8859-1

Heh, I'm a programmer. I have to admit though, that I very rarely check my
return value for null after vars.get. I figure if my BSF sampler fails with
a null pointer exception, I should know what's going on. Using "" + for
string conversion is probably a little less efficient than
Long.toString(variable), since you're creating some extra temporary strings
that you'll have to garbage collect later on. It probably wouldn't make a
measurable difference in your test, unless you looped through doing it a few
thousand times or using a multi-megabyte String. A system I used to work on
would store 30+ megabyte Strings on a regular basis. You definitely don't
want to create any more copies of those than you have to!

-- 
Bruce Ide
FlyingRhenquest@gmail.com

--00151744109cf8464b04ad9d3b4e--