jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject Re: About Backend & Backend Listener Implementation
Date Wed, 01 Jan 2014 22:30:09 GMT
I don't see why the calculations should be done by JMeter.
Not everyone will necessarily need all the ones proposed - and some
may want additional calculations done on the data.

I would prefer to see just an API for storing just the raw data.
This should ideally be extendable to cater for more raw data items.
Not sure I can think of any immediately, but as I recall latency was
not originally measured.

Anything further should be done in the implementation.

Perhaps the implementations should consist of a GUI Config element (or
similar) which is used to provide the settings, plus a separate class
to implement the data sink.

The Listener would then display a list of implementations for the user
to choose.

Or perhaps the interface could be more like the Java Sampler, where
the implementation class contains details of the settings that are
then diplayed on the GUI. That should make it simpler to implement the

On 1 January 2014 21:39, Philippe Mouawad <> wrote:
> One last point:
> - properties required for one implementation of backend will use
>, for example (jdbc url, login,password,
> graphite host, port, database)
> On Wed, Jan 1, 2014 at 10:35 PM, Philippe Mouawad <
>> wrote:
>> Hello,
>> To be sure we agree I propose the following way to implement it:
>> - BackendListener will be similar to current Graphite Listener attached in
>> Patch  for
>> - Any Graphite specificity will be moved out
>> So:
>> - Current metrics will be named the same
>> - Percentiles will be computed in the same way based on commons-math3 (so
>> 1.2 Mb increase)
>> - Filtering will remain
>> - Listener will search for Backend implementations in BeanInfo class to
>> propose a list of backends to user that it will later use
>> --
>> Regards.
>> Philippe M
> --
> Cordialement.
> Philippe Mouawad.

View raw message