On Tue, 18 Jan 2005 14:42:11 + (UTC), Olve Hansen
<[EMAIL PROTECTED]> wrote:
> Peter Lin gmail.com> writes:
>
> >
> > yeah, that has been fixed. it was a bug in the caption and in the
> > weight calculation for the health tab. the fix was checked in a few
> > months back.
> >
> > peter
> >
>
Hi Olve,
I ran the test locally on my laptop and the graph is correct. what I
did to test was to create a test plan with 1 thread group with 100
threads hitting "/" on tomcat. A second thread hits the status
servlet.
the ramp up time for the first thread is 100.
I also opened the status servlet
it occurred to me, it could be the graph class and how it draws the
line. if you can give me a bit more information, it would help
diagnose the problem. thanks
peter
On Tue, 18 Jan 2005 14:42:11 + (UTC), Olve Hansen
<[EMAIL PROTECTED]> wrote:
> Peter Lin gmail.com> writes:
>
> >
> > yeah,
the current implementation does this.
double memdiv = (double)usedMem/(double)totMem;
double memWeight = DEFAULT_MEMORY_FACTOR * memdiv;
the load factor is 50, so as the memory usage increases, memdiv should
get closer to 1. That would mean if the memory used is 90%.
load (blue line) would be 45
let me double check, I thought I corrected it, but I could be smoking crack.
peter
On Tue, 18 Jan 2005 14:42:11 + (UTC), Olve Hansen
<[EMAIL PROTECTED]> wrote:
> Peter Lin gmail.com> writes:
>
> >
> > yeah, that has been fixed. it was a bug in the caption and in the
> > weight calculation
Peter Lin gmail.com> writes:
>
> yeah, that has been fixed. it was a bug in the caption and in the
> weight calculation for the health tab. the fix was checked in a few
> months back.
>
> peter
>
I have experienced the same error, but it is not fixed in 2.0.2, nor the nightly
build from jaka
Oh, great. Was it fixed since 2.0.2, then? That's what I'm running. If so,
I'll get a nightly build and try my luck.
Thanks,
S
-Original Message-
From: Peter Lin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 08, 2004 10:43 AM
To: JMeter Users List
Subject: Re:
yeah, that has been fixed. it was a bug in the caption and in the
weight calculation for the health tab. the fix was checked in a few
months back.
peter
On Wed, 8 Dec 2004 10:35:32 -0500, Bartlett, Sarah <[EMAIL PROTECTED]> wrote:
> I've been using the Monitor Results Listener in combination w
I've been using the Monitor Results Listener in combination with a monitoring
test plan to watch the impact of my tests on the server. It seems as though
the memory % function is inverted thereby also skewing the load measurement.
As my load increases the used memory goes down, which is opposi
9 matches
Mail list logo
