>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... <czh...@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 >
