jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepak Shetty <shet...@gmail.com>
Subject Re: RE: question about duration assertion
Date Wed, 30 Mar 2011 12:49:09 GMT
>I figured it would give an OutOfMemory exception at some point,
what you are getting isnt the standard OutOfMemory.
>When I check the IIS logs, I see the response time did not go over 1000 ms.
Unless your CPU is pegged at 100% I dont see how this can happen.
You can verify the times you are getting by running another standalone
jmeter on a different machine for a single thread at the same time as your
main test.


On Wed, Mar 30, 2011 at 3:44 AM, Cor-Paul Bezemer <c.bezemer@tudelft.nl>wrote:

> Ah thanks, this indeed fixed the first OutOfMemory error. I figured it
> would
> give an OutOfMemory exception at some point, but did not expect it to
> happen
> so soon.
>
> Changing the threadcount to 500 allows me to run a complete test without
> OutOfMemory errors (yey!), however, the AutoStop plugin still stops the
> test
> because the average response time measured by JMeter is > 20000ms.. When I
> check the IIS logs, I see the response time did not go over 1000 ms.
>
> (I'm still running on a local network so network latency shouldn't be the
> problem...)
>
> -----Original Message-----
> From: Deepak Shetty [mailto:shettyd@gmail.com]
> Sent: woensdag 30 maart 2011 12:22
> To: JMeter Users List
> Subject: Re: RE: question about duration assertion
>
> i should also add , reduce your xmx (i think you mentioned it as 1.5g for a
> pc with 2g ram). You might also reduce the perm size and see
>
> On Wed, Mar 30, 2011 at 3:17 AM, Deepak Shetty <shettyd@gmail.com> wrote:
>
> > Ah i see you are using the Stepping Thread Group which I dont have much
> > familiarity with but your count of 10,000 seems too high - I suppose
> Andrey
> > ill weigh in but it sounds as if its attempting to create all threads
> right
> > at the start
> >  reduce this to a much lower value(with sufficient ramp up times) and use
> > multiple JMeter instances on different servers if you want a higher
> > concurrent load. Or temporarily try with the standard thread group (with
> a
> > big enough ramp up for your number of threads)
> >
> > You probably see discrepancies in time because of your OOM(Im assuming
> this
> > is the same cant create native thread) and because you seem to be using
> too
> > many threads due to which the overhead on the client probably gets you a
> > much higher value on your times.
> >
> > regards
> > deepak
> >
> >
> >
> >
> >
> > On Wed, Mar 30, 2011 at 2:11 AM, Cor-Paul Bezemer
> <c.bezemer@tudelft.nl>wrote:
> >
> >> I have tried to run JMeter from a different machine, but the same
> occurs..
> >> In fact, I still get the OutOfMemory issue after 10 threads :/ After
> this
> >> the test continues and right before I get the following OutOfMemory
> >> exception, the Autostop plugin tells me that the avg response time is
> over
> >> 20s (which it was not as I can see from my IIS log). Can anyone perhaps
> >> try
> >> this testcase and see if they get the same result as I do? (make sure to
> >> fill in the URL, should happen with all URLs).
> >>
> >> <?xml version="1.0" encoding="UTF-8"?>
> >> <jmeterTestPlan version="1.2" properties="2.1">
> >>  <hashTree>
> >>    <TestPlan guiclass="TestPlanGui" testclass="TestPlan" testname="Test
> >> Plan" enabled="true">
> >>      <stringProp name="TestPlan.comments"></stringProp>
> >>      <boolProp name="TestPlan.functional_mode">false</boolProp>
> >>      <boolProp name="TestPlan.serialize_threadgroups">false</boolProp>
> >>      <elementProp name="TestPlan.user_defined_variables"
> >> elementType="Arguments" guiclass="ArgumentsPanel" testclass="Arguments"
> >> testname="User Defined Variables" enabled="true">
> >>        <collectionProp name="Arguments.arguments"/>
> >>      </elementProp>
> >>      <stringProp name="TestPlan.user_define_classpath"></stringProp>
> >>    </TestPlan>
> >>    <hashTree>
> >>      <CookieManager guiclass="CookiePanel" testclass="CookieManager"
> >> testname="HTTP Cookie Manager" enabled="true">
> >>        <collectionProp name="CookieManager.cookies"/>
> >>        <boolProp
> name="CookieManager.clearEachIteration">false</boolProp>
> >>        <stringProp name="CookieManager.policy">rfc2109</stringProp>
> >>      </CookieManager>
> >>      <hashTree/>
> >>      <kg.apc.jmeter.threads.SteppingThreadGroup
> >> guiclass="kg.apc.jmeter.threads.SteppingThreadGroupGui"
> >> testclass="kg.apc.jmeter.threads.SteppingThreadGroup" testname="Stepping
> >> Thread Group" enabled="true">
> >>        <stringProp
> >> name="ThreadGroup.on_sample_error">stoptest</stringProp>
> >>        <stringProp name="ThreadGroup.num_threads">10000</stringProp>
> >>        <stringProp name="Threads initial delay">0</stringProp>
> >>        <stringProp name="Start users count">10</stringProp>
> >>        <stringProp name="Start users period">5</stringProp>
> >>        <stringProp name="Stop users count">5</stringProp>
> >>        <stringProp name="Stop users period">1</stringProp>
> >>        <stringProp name="flighttime">0</stringProp>
> >>        <elementProp name="ThreadGroup.main_controller"
> >> elementType="LoopController" guiclass="LoopControlPanel"
> >> testclass="LoopController" testname="Loop Controller" enabled="true">
> >>          <boolProp
> name="LoopController.continue_forever">false</boolProp>
> >>          <intProp name="LoopController.loops">-1</intProp>
> >>        </elementProp>
> >>      </kg.apc.jmeter.threads.SteppingThreadGroup>
> >>      <hashTree>
> >>        <ConfigTestElement guiclass="HttpDefaultsGui"
> >> testclass="ConfigTestElement" testname="HTTP Request Defaults"
> >> enabled="true">
> >>          <elementProp name="HTTPsampler.Arguments"
> elementType="Arguments"
> >> guiclass="HTTPArgumentsPanel" testclass="Arguments" testname="User
> Defined
> >> Variables" enabled="true">
> >>            <collectionProp name="Arguments.arguments"/>
> >>          </elementProp>
> >>          <stringProp name="HTTPSampler.domain">server</stringProp>
> >>          <stringProp name="HTTPSampler.port">666</stringProp>
> >>          <stringProp name="HTTPSampler.connect_timeout"></stringProp>
> >>          <stringProp name="HTTPSampler.response_timeout"></stringProp>
> >>          <stringProp name="HTTPSampler.protocol"></stringProp>
> >>          <stringProp name="HTTPSampler.contentEncoding"></stringProp>
> >>          <stringProp name="HTTPSampler.path">/path/</stringProp>
> >>        </ConfigTestElement>
> >>        <hashTree/>
> >>        <HTTPSampler guiclass="HttpTestSampleGui" testclass="HTTPSampler"
> >> testname="HTTP Request" enabled="true">
> >>          <elementProp name="HTTPsampler.Arguments"
> elementType="Arguments"
> >> guiclass="HTTPArgumentsPanel" testclass="Arguments" testname="User
> Defined
> >> Variables" enabled="true">
> >>            <collectionProp name="Arguments.arguments"/>
> >>          </elementProp>
> >>          <stringProp name="HTTPSampler.domain"></stringProp>
> >>          <stringProp name="HTTPSampler.port"></stringProp>
> >>          <stringProp name="HTTPSampler.connect_timeout"></stringProp>
> >>          <stringProp name="HTTPSampler.response_timeout"></stringProp>
> >>          <stringProp name="HTTPSampler.protocol"></stringProp>
> >>          <stringProp name="HTTPSampler.contentEncoding"></stringProp>
> >>          <stringProp
> >>
> >>
>
> name="HTTPSampler.path">/nopcommerce/AppExI_TestCases/tc1_r_large_file.aspx<
> >> /stringProp>
> >>          <stringProp name="HTTPSampler.method">GET</stringProp>
> >>          <boolProp name="HTTPSampler.follow_redirects">true</boolProp>
> >>          <boolProp name="HTTPSampler.auto_redirects">false</boolProp>
> >>          <boolProp name="HTTPSampler.use_keepalive">true</boolProp>
> >>          <boolProp name="HTTPSampler.DO_MULTIPART_POST">false</boolProp>
> >>          <boolProp name="HTTPSampler.monitor">false</boolProp>
> >>          <stringProp name="HTTPSampler.embedded_url_re"></stringProp>
> >>        </HTTPSampler>
> >>        <hashTree/>
> >>         <kg.apc.jmeter.reporters.AutoStop
> >> guiclass="kg.apc.jmeter.reporters.AutoStopGui"
> >> testclass="kg.apc.jmeter.reporters.AutoStop" testname="jp@gc - AutoStop
> >> Listener" enabled="true">
> >>          <stringProp name="avg_response_time">20000</stringProp>
> >>          <stringProp name="avg_response_time_length">5</stringProp>
> >>          <stringProp name="error_rate">50</stringProp>
> >>          <stringProp name="error_rate_length">10</stringProp>
> >>          <stringProp name="avg_response_latency">0</stringProp>
> >>          <stringProp name="avg_response_latency_length">10</stringProp>
> >>        </kg.apc.jmeter.reporters.AutoStop>
> >>        <hashTree/>
> >>      </hashTree>
> >>    </hashTree>
> >>  </hashTree>
> >> </jmeterTestPlan>
> >>
> >> -----Original Message-----
> >> From: Deepak Shetty [mailto:shettyd@gmail.com]
> >> Sent: dinsdag 29 maart 2011 18:03
> >> To: JMeter Users List
> >> Subject: Re: RE: question about duration assertion
> >>
> >> If you are running jmeter on the same machine as your server expect
> weird
> >> results. Run jmeter on a different machine
> >> On Mar 29, 2011 8:53 AM, "Cor-Paul Bezemer" <c.bezemer@tudelft.nl>
> wrote:
> >> > I'm using Win 7, Java 1.6.0, Jmeter 2.4 and I'm not running it from
> >> inside
> >> a
> >> > virtual machine.
> >> >
> >> > -----Original Message-----
> >> > From: sebb [mailto:sebbaz@gmail.com]
> >> > Sent: dinsdag 29 maart 2011 17:21
> >> > To: JMeter Users List
> >> > Subject: Re: question about duration assertion
> >> >
> >> > Rather strange.
> >> >
> >> > What OS are you using? JVM? JMeter version?
> >> >
> >> > Are you running it in a virtual machine?
> >> > That can cause problems with clocks.
> >> >
> >> > On 29 March 2011 15:33, Cor-Paul Bezemer <c.bezemer@tudelft.nl>
> wrote:
> >> >> Hmmmm OK... The strange thing is that I don't really see my java
> >> process
> >> >> using a large amount of memory.
> >> >>
> >> >> The memory settings are HEAP=-Xms1536m -Xmx1536m and the actual
> memory
> >> > usage
> >> >> does not come near this.
> >> >>
> >> >>
> >> >> -----Original Message-----
> >> >> From: apc [mailto:apc@apc.kg]
> >> >> Sent: dinsdag 29 maart 2011 16:29
> >> >> To: jmeter-user@jakarta.apache.org
> >> >> Subject: RE: question about duration assertion
> >> >>
> >> >> A-ha! OutOfMemory!
> >> >>
> >> >> This means that your JMeter works with resource problems... And this
> >> may
> >> >> cause a lot of side effects.
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >>
> >> >
> >>
> >>
>
> http://jmeter.512774.n5.nabble.com/question-about-duration-assertion-tp42690
> >> >> 21p4269485.html
> >> >> Sent from the JMeter - User mailing list archive at Nabble.com.
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >> >>
> >> >>
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >> >>
> >> >>
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >> >
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >> >
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >>
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>

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