Yes, James. I am speaking of LoadUI for load testing, but the issue
that I am talking about is just for the response time comparisons for
a single user web service test in both soapUI & LR.
On Sep 7, 9:54 pm, "James Pulley" <
loadrunner-li...@jamespulley.com>
wrote:
> Start documenting differences, from the location, size and configuration of
> load generators to the nature of data involved in the calls. Performance
> tests are the clearest example of the butterfly effect in place that I can
> think of, where small differences in initial conditions make for
> dramatically different results at the end of the test.
>
> Be certain that you are deploying both tools in their optimal models.
> Eliminate virtualization if you have that in place. Use exactly the same
> load generators (where possible).
>
> And I guess you are speaking of LoadUI, notSOAPUIfor performance testing.
>
>
>
>
>
>
>
> -----Original Message-----
> From:
lr-loa...@googlegroups.com [mailto:
lr-loa...@googlegroups.com]
>
> On Behalf Of Britto Louis
> Sent: Wednesday, September 07, 2011 12:38 PM
> To:LoadRunner
> Subject: Re: Web services Response times comparison:SoapUIVsLoadrunner
>
> Thanks for the steps James.
>
> I have made sure of all the aspects to make sure that the requests and
> responses are EXACTLY the same in bothsoapUIand LR.
> Even excluding the wasted time of LR, the difference is quite
> significant, withsoapUIgiving significantly lesser response time.
>
> So again, any ideas on this issue, are welcome!
>
> Thanks
> Britto
>
> On Sep 6, 8:29 pm, James Pulley <
loadrunner-li...@jamespulley.com>
> wrote:
> > Define your own benchmark. Implement the benchmark in both of your
> > test tools. Measure not only the output but also how long it took to
> > generate the inputs and also to generate the output to the same level
> > of information. To be fairest, use an expert for each of the tools
> > to run the test based upon the provided documentation for the
> > benchmark - This way you get a feel for the most efficient delivery of
> > each tool. Or, conversely, you could use someone who knows neither
> > tool well or at all to get a feel for a worst case scenario.
>
> >LoadRunneralso has the ability to measure its own API time, a concept
> > called wasted time, so it would be interesting to note if you could
> > pull an equivalent level of information out of the other tools on the
> > tool imposed overhead.
>
> > James Pulley,
http://www.loadrunnerbythehour.com
>
> > On Sep 5, 11:38 am, Rupesh Garg <
rupeshgar...@gmail.com> wrote:
>
> > > I would like to know same level of comparison for the Load Runner and
> Jmeter
> > > Rupesh
> > > 9160002744
>
> > >
http://rupeshkgarg.blogspot.com/http://www.artofliving.org
>
> > > M. K. Gandhi - ""Live as if you were to die tomorrow. Learn as if you
> were
> > > to live forever."
>
> > > On Mon, Sep 5, 2011 at 11:59 AM, Britto Louis
> <
britto.lo...@gmail.com>wrote:
>
> > > > Hi All,
> > > > I have been usingLoadRunnerextensively for web performance testing,