Hello Chaitanya, Can you try with current nightly build and give us feedback. There have been 2 big optimisations regarding memory and CPU.
Also check that you regexp extractor don't use option Body (unescaped) Regards Philippe On Wednesday, December 5, 2012, Enric Jaen wrote: > > > Upps, my mistake. These flags doesn't apply here as you aren't getting any > outOfMemory. > > In any case, with java6 you can create a snapshot of the heap with a java > profiler to get a more exact idea of what objects are consuming the memory. > > HTH > /Enric Jaen > > > > ________________________________ > De: Enric Jaen <[email protected] <javascript:;>> > Para: JMeter Users List <[email protected] <javascript:;>> > Enviado: Miércoles 5 de diciembre de 2012 9:31 > Asunto: Re: Why does Jmeter have a huge memory footprint? > > Maybe you could add these params to the JVM to generate a .hprof file : > > -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<your log dir> > > > to be analysed with a java profiler [1] what is eating the memory. > > HTH > /Enric Jaen > > > [1] for example eclipse MAT plugin http://www.eclipse.org/mat/ > > > > ________________________________ > De: chaitanya bhatt <[email protected]> > Para: JMeter Users List <[email protected]> > Enviado: Miércoles 5 de diciembre de 2012 0:27 > Asunto: Re: Why does Jmeter have a huge memory footprint? > > Still working on it. Sorry Philippe and Smuel. I will try my best to log > the defect within the next two days. > > Thanks > Chaitanya M Bhatt > > > On Tue, Dec 4, 2012 at 2:13 PM, Philippe Mouawad < > [email protected] > > wrote: > > > Hello, > > Still no Bugzilla created. > > > > By the way what is the sizes of your responses , zipped and not zipped ? > > > > Thanks > > Regards > > Philippe > > > > On Fri, Nov 30, 2012 at 12:55 AM, chaitanya bhatt < > > [email protected] > > > wrote: > > > > > Sure Philippe. > > > > > > Thanks a ton! > > > Chaitanya > > > > > > On Thu, Nov 29, 2012 at 2:25 PM, Philippe Mouawad < > > > [email protected]> wrote: > > > > > > > Hello, > > > > I suggest you open a bugzilla (there is no one for that) and provide: > > > > > > > > - jmeter.properties and user.properties file > > > > - jmeter.log > > > > - jmeter file you used > > > > - Test Plan > > > > - And as you seem to have evaluated the memory some screenshots of > > > > consumptions you are talking about > > > > > > > > > > > > Regards > > > > > > > > Philippe > > > > > > > > On Thu, Nov 29, 2012 at 10:52 PM, chaitanya bhatt < > > > > [email protected] > > > > > wrote: > > > > > > > > > I am running the test via console/terminal. > > > > > I am not saving transaction response times or responses to files. > > > > > I am measuring response time directly from the Wily (servlet > > response > > > > > time). > > > > > I have response assertions which checks the body of the HTTP > > response. > > > > > The IF controller just evaluates a variable and checks if the > value > > > > > exceeds number 2. Interpreter condition and Evaluate for all > children > > > is > > > > > Unchecked. > > > > > Basically, I have made sure that the test suit is as leane as > > > possible. > > > > > I don't have any soft of non-html/non-json/non-xml HTTP resource > > > > requests. > > > > > > > > > > Thanks > > > > > Chaitanya > > > > > > > > > > On Thu, Nov 29, 2012 at 1:27 PM, Philippe Mouawad < > > > > > [email protected]> wrote: > > > > > > > > > > > Hello, > > > > > > > > > > > > On Thu, Nov 29, 2012 at 10:12 PM, chaitanya bhatt < > > > > > > [email protected] > > > > > > > wrote: > > > > > > > > > > > > > Thanks for replying Philippe! > > > > > > > > > > > > > > I noticed that the test cases you guys used to test the > > performance > > > > of > > > > > > > Jmeter is far to small than real world -- Cordialement. Philippe Mouawad.
