Scaling input results

[Patrick Loijens]

Hi.

I'm using perfbase to compare different networktypes using different
benchmarktools. A bit to late I noticed it's not possible to exchange
data between experiment-setups, so I need to put all data in one
experiment. No problem so far.

The problem is scaling of the input of the benchmark results, since the
results e.q. for bandwidth are -depending on the benchmark- in bit or
bytes and 2^20 or 10^6.  I would like to scale the data to 10^6 bits.
Until now I gathered the data with
<tabular_location> and <tabular_value>,  but if I'm reading the dtd
correct, these options don't allow the data to be scaled.

The element "term" seems to be what I'm looking for, which seems only
supported with <derived_parameter>. Correct me if I'm wrong, but if I
want to use this for my purposes I need a field in the experiment which
gets the data from the output and stores it for further use and a second
field which stores the output of <derived_parameter> using the value of
the first field. Thus  for every result value 2 fields need to be created.

So my question is: is this correct c.q. is there a more simple version
or another solution?

A completely other question: is it correct that one can't use a
parametername "opt_2" (without quotes) in queries?

And last, a nice to have: a possibility to compare results between
experiments (change-request).

Thanks in advance,
Patrick Loijens

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Joachim Worringen-4]

Patrick Loijens wrote:
> So my question is: is this correct c.q. is there a more simple version
> or another solution?

Did you try the attribute "scale" of <named_location> or <tabular_value>
(see pb_input.dtd)? It will scale the numerical input value with the
given factor. I.e., to scale from Mbit/s to MB/s, do 'scale="0.125"'.

> A completely other question: is it correct that one can't use a
> parametername "opt_2" (without quotes) in queries?

At least not on purpose. What happens if you do so?

> And last, a nice to have: a possibility to compare results between
> experiments (change-request).

I don't think this makes sense. If benchmarks produce comparable data,
put them into one experiment. And it's a significant implmentation
overhead, too.

  Joachim

--
Joachim Worringen, Software Architect, Dolphin Interconnect Solutions
phone ++49/(0)228/324 08 17 - http://www.dolphinics.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Patrick Loijens]

Joachim Worringen schrieb:

> Patrick Loijens wrote:
>
>> So my question is: is this correct c.q. is there a more simple
>> version or another solution?
>
> Did you try the attribute "scale" of <named_location> or
> <tabular_value> (see pb_input.dtd)? It will scale the numerical input
> value with the given factor. I.e., to scale from Mbit/s to MB/s, do
> 'scale="0.125"'.


Tried it, yes, but it gave (wenn using decimal values) an error,
something like "not numerical" or "no CDATA". Since this option didn't
have a comment in the dtd, I didn't know if it was supposed to do what
the name suggested.
Now tried it again and it works. Can't tell what I did wrong, I know I
tested with both "." and "," .
A short comment in the input.dtd would be nice.

>
>> A completely other question: is it correct that one can't use a
>> parametername "opt_2" (without quotes) in queries?
>
> At least not on purpose. What happens if you do so?

Can't reproduse this one either. Had this problem a few months ago, but
in between we updated postsql and perfbase....

Thanks!

Patrick

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...