On 26/09/2008, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi > Thanks for the reply. > > > > -----Original Message----- > > From: sebb [mailto:[EMAIL PROTECTED] > > Sent: 26 September 2008 15:41 > > To: JMeter Users List > > Subject: Re: usage of spline graph > > > > On 26/09/2008, [EMAIL PROTECTED] > > <[EMAIL PROTECTED]> wrote: > > > Hi > > > I have scoured the documentation for an explanation of the spline > > > visualizer but it is a bit scarce. > > > > The document says: > > > > "The Spline Visualizer provides a view of all sample times > > from the start of the test till the end, regardless of how > > many samples have been taken. The spline has 10 points, each > > representing 10% of the samples, and connected using spline > > logic to show a single continuous line." > > > I saw that bit in the documentation. > > > > > > It does not say that "Incoming" means current. > > > > The samples are divided into 10 batches (in order of > > occurrence) and the average of each batch is used as the > > value of the point. > > > > The 10 points are then plotted using a spline interpolation. > > > > > Could anyone explain what usefull > > > information can be obtained from looking at the spline > > graph. I have > > > watched it a few time during a test but am not sure what > > deductions I > > > should be making. > > > > Sorry, I've no idea. > > > > Perhaps none, as the graph is auto ranging and the limits are > > not shown... > > > > > Obviously someone found it usefull enough to include it as default part > of jmeter
Unfortunately they did not document it... > I was just hoping that someone could shed some light on > interpretations. To me it shows that my application's response time is > erratic during startup and then stabbilizes. I'm not even sure that's true. I've just done a dummy test using the Java Request sampler with a constant time of 200ms. Sample times are all in the range 203ms to 204ms yet the spline curve wanders all over the place, even after 4000 samples. I suppose it might work better if the lower bound of the graph was zero, rather than the minimum. As it stands, it looks like every graph will always hit both the top and bottom. If there are only small variations they will be magnified until they fit the limits of the graph. > If the usage is that simple > then great but then I do feel the docs should be a bit more clear on it. > If someone could confirm/deny this I would gladly make a documentation > change. Documentation patches are always welcome. > > Regards > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > > > --------------------------------------------------------------------- > 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]
