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 + thread weight memory % (orange line) would be 90 what you should see at runtime, is the load will increase until the JVM allocates more memory. Once the server reaches a stable point, the memory usage should remain relatively constant and show a regular pattern. http://cvs.apache.org/viewcvs.cgi/jakarta-jmeter/src/monitor/components/org/apache/jmeter/monitor/util/Stats.java?rev=1.9&view=markup I'll try to run a test at lunch. What kind of behavior do you expect? I'm not sure I understand the exact problem you are seeing. peter On Tue, 18 Jan 2005 14:42:11 +0000 (UTC), Olve Hansen <[EMAIL PROTECTED]> wrote: > Peter Lin <woolfel <at> 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 jakarta-jmeter-2_0.20050109, which is the most recent. Do I have to > download everything from CVS, or will there be antorher nightly build out, > incorporating this fix? > > I really need the Monitor Results, it is a really great piece of work, but as > it > is now, the load goes down as memory usage increases :-( > > Hope this can be fixed soon. > > Thanks, > Olve S. Hansen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
