You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by "Chian Zhong..." <cz...@modeln.com> on 2011/05/16 22:52:45 UTC
monitoring the load run
Hi:
My app is fairly slow I have to say, although no one knows where does the
slowness come from. I've developed a simple JMeter script that navigates to
different pages etc, and I'm able to run it with 1 or 2 users and monitor
the result from result tree.
Now I've added 40 users to it with 100 seconds ramp up time, Jmeter starts
to show me the busy square icon on the right
upper corner with all 40 sessions/users, as I don't see anything changes on
the result table and I'm suggested not to user the result tree to "watch"
it,
what's the best way for me to see if it is jmeter being extremly busy on its
UI or something is not right on my app?
I opened the browser on a different box and app seemed to hold on ok, does
this imply that I just have to wait till Jmeter "finishes"
whatever it is doing? I tried to wait over the weekend and I suspected that
something is not right on the Jmeter, so anyone knows what's the best way to
see what JMeter is busying about?
am I the only one who have seen such behavior? by the way, my memory setting
was 14M to 256 MB for new, 14 M to 256 for heap/
any tip?
Thanks
Chian
Re: monitoring the load run
Posted by Deepak Shetty <sh...@gmail.com>.
Hi
>I suspect that last 64m needs to be 1024m instead.
no perm size is usually in this range (or 128M).
If you stop the jmeter threads after they run for sometime , can you not see
the jmeter.log file?
regards
deepak
On Mon, May 16, 2011 at 2:22 PM, Chian Zhong... <cz...@modeln.com> wrote:
> Deepak:
>
> Thanks for the tip. the jmeter.log file can not be opened during the run,
> my
> windows complains other program is using it. Here is my complete parameters
> for jmeter on windows:
>
> set HEAP=-Xms512m -Xmx1024m
> set NEW=-XX:NewSize=128m -XX:MaxNewSize=256m
> set SURVIVOR=-XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=50%
> set TENURING=-XX:MaxTenuringThreshold=2
> set EVACUATION=-XX:MaxLiveObjectEvacuationRatio=20%
> set RMIGC=-Dsun.rmi.dgc.client.gcInterval=600000
> -Dsun.rmi.dgc.server.gcInterval=600000
> set PERM=-XX:PermSize=64m -XX:MaxPermSize=64m
>
> I suspect that last 64m needs to be 1024m instead. is this typical?
> Thanks
> Chian
>
>
> On Mon, May 16, 2011 at 1:57 PM, Deepak Shetty <sh...@gmail.com> wrote:
>
> > >and I'm suggested not to user the result tree to "watch" it,
> > You can watch when you are debugging something.
> >
> > > does this imply that I just have to wait till Jmeter "finishes"
> whatever
> > it is doing?
> > You should be able to see the results as they finish if you enable some
> > listeners , like view summary report
> > Check jmeter.log for errors
> > >14 M to 256 for heap
> > seems a bit on the lower side , but shouldnt cause the problems you see.
> In
> > any case I'd enable some listeners and see what I get and check
> jmeter.log
> >
> > regards
> > deepak
> >
> > On Mon, May 16, 2011 at 1:52 PM, Chian Zhong... <cz...@modeln.com>
> wrote:
> >
> > > Hi:
> > >
> > > My app is fairly slow I have to say, although no one knows where does
> the
> > > slowness come from. I've developed a simple JMeter script that
> navigates
> > to
> > > different pages etc, and I'm able to run it with 1 or 2 users and
> monitor
> > > the result from result tree.
> > >
> > > Now I've added 40 users to it with 100 seconds ramp up time, Jmeter
> > starts
> > > to show me the busy square icon on the right
> > > upper corner with all 40 sessions/users, as I don't see anything
> changes
> > on
> > > the result table and I'm suggested not to user the result tree to
> "watch"
> > > it,
> > > what's the best way for me to see if it is jmeter being extremly busy
> on
> > > its
> > > UI or something is not right on my app?
> > >
> > > I opened the browser on a different box and app seemed to hold on ok,
> > does
> > > this imply that I just have to wait till Jmeter "finishes"
> > > whatever it is doing? I tried to wait over the weekend and I suspected
> > that
> > > something is not right on the Jmeter, so anyone knows what's the best
> way
> > > to
> > > see what JMeter is busying about?
> > >
> > > am I the only one who have seen such behavior? by the way, my memory
> > > setting
> > > was 14M to 256 MB for new, 14 M to 256 for heap/
> > > any tip?
> > >
> > > Thanks
> > > Chian
> > >
> >
>
Re: monitoring the load run
Posted by "Chian Zhong..." <cz...@modeln.com>.
thanks! I'm installing notepad++, the tool is powerful!...
On Mon, May 16, 2011 at 3:41 PM, sebb <se...@gmail.com> wrote:
> On 16 May 2011 22:22, Chian Zhong... <cz...@modeln.com> wrote:
> > Deepak:
> >
> > Thanks for the tip. the jmeter.log file can not be opened during the run,
> my
> > windows complains other program is using it.
>
> Use a different editor, e.g. Notepad can open the active JMeter log files.
> As can Context, Notepad++, PsPad and no doubt many others.
>
> > Here is my complete parameters
> > for jmeter on windows:
> >
> > set HEAP=-Xms512m -Xmx1024m
> > set NEW=-XX:NewSize=128m -XX:MaxNewSize=256m
> > set SURVIVOR=-XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=50%
> > set TENURING=-XX:MaxTenuringThreshold=2
> > set EVACUATION=-XX:MaxLiveObjectEvacuationRatio=20%
> > set RMIGC=-Dsun.rmi.dgc.client.gcInterval=600000
> > -Dsun.rmi.dgc.server.gcInterval=600000
> > set PERM=-XX:PermSize=64m -XX:MaxPermSize=64m
> >
> > I suspect that last 64m needs to be 1024m instead. is this typical?
> > Thanks
> > Chian
> >
> >
> > On Mon, May 16, 2011 at 1:57 PM, Deepak Shetty <sh...@gmail.com>
> wrote:
> >
> >> >and I'm suggested not to user the result tree to "watch" it,
> >> You can watch when you are debugging something.
> >>
> >> > does this imply that I just have to wait till Jmeter "finishes"
> whatever
> >> it is doing?
> >> You should be able to see the results as they finish if you enable some
> >> listeners , like view summary report
> >> Check jmeter.log for errors
> >> >14 M to 256 for heap
> >> seems a bit on the lower side , but shouldnt cause the problems you see.
> In
> >> any case I'd enable some listeners and see what I get and check
> jmeter.log
> >>
> >> regards
> >> deepak
> >>
> >> On Mon, May 16, 2011 at 1:52 PM, Chian Zhong... <cz...@modeln.com>
> wrote:
> >>
> >> > Hi:
> >> >
> >> > My app is fairly slow I have to say, although no one knows where does
> the
> >> > slowness come from. I've developed a simple JMeter script that
> navigates
> >> to
> >> > different pages etc, and I'm able to run it with 1 or 2 users and
> monitor
> >> > the result from result tree.
> >> >
> >> > Now I've added 40 users to it with 100 seconds ramp up time, Jmeter
> >> starts
> >> > to show me the busy square icon on the right
> >> > upper corner with all 40 sessions/users, as I don't see anything
> changes
> >> on
> >> > the result table and I'm suggested not to user the result tree to
> "watch"
> >> > it,
> >> > what's the best way for me to see if it is jmeter being extremly busy
> on
> >> > its
> >> > UI or something is not right on my app?
> >> >
> >> > I opened the browser on a different box and app seemed to hold on ok,
> >> does
> >> > this imply that I just have to wait till Jmeter "finishes"
> >> > whatever it is doing? I tried to wait over the weekend and I suspected
> >> that
> >> > something is not right on the Jmeter, so anyone knows what's the best
> way
> >> > to
> >> > see what JMeter is busying about?
> >> >
> >> > am I the only one who have seen such behavior? by the way, my memory
> >> > setting
> >> > was 14M to 256 MB for new, 14 M to 256 for heap/
> >> > any tip?
> >> >
> >> > Thanks
> >> > Chian
> >> >
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
Re: monitoring the load run
Posted by sebb <se...@gmail.com>.
On 16 May 2011 22:22, Chian Zhong... <cz...@modeln.com> wrote:
> Deepak:
>
> Thanks for the tip. the jmeter.log file can not be opened during the run, my
> windows complains other program is using it.
Use a different editor, e.g. Notepad can open the active JMeter log files.
As can Context, Notepad++, PsPad and no doubt many others.
> Here is my complete parameters
> for jmeter on windows:
>
> set HEAP=-Xms512m -Xmx1024m
> set NEW=-XX:NewSize=128m -XX:MaxNewSize=256m
> set SURVIVOR=-XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=50%
> set TENURING=-XX:MaxTenuringThreshold=2
> set EVACUATION=-XX:MaxLiveObjectEvacuationRatio=20%
> set RMIGC=-Dsun.rmi.dgc.client.gcInterval=600000
> -Dsun.rmi.dgc.server.gcInterval=600000
> set PERM=-XX:PermSize=64m -XX:MaxPermSize=64m
>
> I suspect that last 64m needs to be 1024m instead. is this typical?
> Thanks
> Chian
>
>
> On Mon, May 16, 2011 at 1:57 PM, Deepak Shetty <sh...@gmail.com> wrote:
>
>> >and I'm suggested not to user the result tree to "watch" it,
>> You can watch when you are debugging something.
>>
>> > does this imply that I just have to wait till Jmeter "finishes" whatever
>> it is doing?
>> You should be able to see the results as they finish if you enable some
>> listeners , like view summary report
>> Check jmeter.log for errors
>> >14 M to 256 for heap
>> seems a bit on the lower side , but shouldnt cause the problems you see. In
>> any case I'd enable some listeners and see what I get and check jmeter.log
>>
>> regards
>> deepak
>>
>> On Mon, May 16, 2011 at 1:52 PM, Chian Zhong... <cz...@modeln.com> wrote:
>>
>> > Hi:
>> >
>> > My app is fairly slow I have to say, although no one knows where does the
>> > slowness come from. I've developed a simple JMeter script that navigates
>> to
>> > different pages etc, and I'm able to run it with 1 or 2 users and monitor
>> > the result from result tree.
>> >
>> > Now I've added 40 users to it with 100 seconds ramp up time, Jmeter
>> starts
>> > to show me the busy square icon on the right
>> > upper corner with all 40 sessions/users, as I don't see anything changes
>> on
>> > the result table and I'm suggested not to user the result tree to "watch"
>> > it,
>> > what's the best way for me to see if it is jmeter being extremly busy on
>> > its
>> > UI or something is not right on my app?
>> >
>> > I opened the browser on a different box and app seemed to hold on ok,
>> does
>> > this imply that I just have to wait till Jmeter "finishes"
>> > whatever it is doing? I tried to wait over the weekend and I suspected
>> that
>> > something is not right on the Jmeter, so anyone knows what's the best way
>> > to
>> > see what JMeter is busying about?
>> >
>> > am I the only one who have seen such behavior? by the way, my memory
>> > setting
>> > was 14M to 256 MB for new, 14 M to 256 for heap/
>> > any tip?
>> >
>> > Thanks
>> > Chian
>> >
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: monitoring the load run
Posted by "Chian Zhong..." <cz...@modeln.com>.
Deepak:
Thanks for the tip. the jmeter.log file can not be opened during the run, my
windows complains other program is using it. Here is my complete parameters
for jmeter on windows:
set HEAP=-Xms512m -Xmx1024m
set NEW=-XX:NewSize=128m -XX:MaxNewSize=256m
set SURVIVOR=-XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=50%
set TENURING=-XX:MaxTenuringThreshold=2
set EVACUATION=-XX:MaxLiveObjectEvacuationRatio=20%
set RMIGC=-Dsun.rmi.dgc.client.gcInterval=600000
-Dsun.rmi.dgc.server.gcInterval=600000
set PERM=-XX:PermSize=64m -XX:MaxPermSize=64m
I suspect that last 64m needs to be 1024m instead. is this typical?
Thanks
Chian
On Mon, May 16, 2011 at 1:57 PM, Deepak Shetty <sh...@gmail.com> wrote:
> >and I'm suggested not to user the result tree to "watch" it,
> You can watch when you are debugging something.
>
> > does this imply that I just have to wait till Jmeter "finishes" whatever
> it is doing?
> You should be able to see the results as they finish if you enable some
> listeners , like view summary report
> Check jmeter.log for errors
> >14 M to 256 for heap
> seems a bit on the lower side , but shouldnt cause the problems you see. In
> any case I'd enable some listeners and see what I get and check jmeter.log
>
> regards
> deepak
>
> On Mon, May 16, 2011 at 1:52 PM, Chian Zhong... <cz...@modeln.com> wrote:
>
> > Hi:
> >
> > My app is fairly slow I have to say, although no one knows where does the
> > slowness come from. I've developed a simple JMeter script that navigates
> to
> > different pages etc, and I'm able to run it with 1 or 2 users and monitor
> > the result from result tree.
> >
> > Now I've added 40 users to it with 100 seconds ramp up time, Jmeter
> starts
> > to show me the busy square icon on the right
> > upper corner with all 40 sessions/users, as I don't see anything changes
> on
> > the result table and I'm suggested not to user the result tree to "watch"
> > it,
> > what's the best way for me to see if it is jmeter being extremly busy on
> > its
> > UI or something is not right on my app?
> >
> > I opened the browser on a different box and app seemed to hold on ok,
> does
> > this imply that I just have to wait till Jmeter "finishes"
> > whatever it is doing? I tried to wait over the weekend and I suspected
> that
> > something is not right on the Jmeter, so anyone knows what's the best way
> > to
> > see what JMeter is busying about?
> >
> > am I the only one who have seen such behavior? by the way, my memory
> > setting
> > was 14M to 256 MB for new, 14 M to 256 for heap/
> > any tip?
> >
> > Thanks
> > Chian
> >
>
Re: monitoring the load run
Posted by Deepak Shetty <sh...@gmail.com>.
>and I'm suggested not to user the result tree to "watch" it,
You can watch when you are debugging something.
> does this imply that I just have to wait till Jmeter "finishes" whatever
it is doing?
You should be able to see the results as they finish if you enable some
listeners , like view summary report
Check jmeter.log for errors
>14 M to 256 for heap
seems a bit on the lower side , but shouldnt cause the problems you see. In
any case I'd enable some listeners and see what I get and check jmeter.log
regards
deepak
On Mon, May 16, 2011 at 1:52 PM, Chian Zhong... <cz...@modeln.com> wrote:
> Hi:
>
> My app is fairly slow I have to say, although no one knows where does the
> slowness come from. I've developed a simple JMeter script that navigates to
> different pages etc, and I'm able to run it with 1 or 2 users and monitor
> the result from result tree.
>
> Now I've added 40 users to it with 100 seconds ramp up time, Jmeter starts
> to show me the busy square icon on the right
> upper corner with all 40 sessions/users, as I don't see anything changes on
> the result table and I'm suggested not to user the result tree to "watch"
> it,
> what's the best way for me to see if it is jmeter being extremly busy on
> its
> UI or something is not right on my app?
>
> I opened the browser on a different box and app seemed to hold on ok, does
> this imply that I just have to wait till Jmeter "finishes"
> whatever it is doing? I tried to wait over the weekend and I suspected that
> something is not right on the Jmeter, so anyone knows what's the best way
> to
> see what JMeter is busying about?
>
> am I the only one who have seen such behavior? by the way, my memory
> setting
> was 14M to 256 MB for new, 14 M to 256 for heap/
> any tip?
>
> Thanks
> Chian
>