[httperf] httperf benchmarking and reporting

[Mark Nottingham]

I was just thinking of key = value, one per line; it's easy to parse,  
and extensible (which is important since much of the value of httperf  
is that it's so modular).

RDF, etc. are way overkill for this.

Cheers,



On 18/07/2008, at 1:51 PM, Theodore Bullock wrote:

> On Fri, 2008-07-18 at 11:32 -0700, Mark Nottingham wrote:
>> Would it be worth having a mode where httperf reports its results in
>> a
>> more normal and machine-friendly way, so that tools can depend on
>> output, and we have more freedom to change the output intended for
>> people?
>
> At WWW2007 last year I had a discussion with a couple people about  
> this
> very topic.  Here is a bit of what I came up with.
>
> CSV
>
> A flat text file with the data entered in a row.
>
> Would need a new option to specify the file name.  If the file doesn't
> exist we create it, with a "header" row.  If it does exist, we just
> append our data to the end of it.
>
> Thus each consecutive run of httperf grows the data set.
>
> I think this is the most appropriate solution for global "end of
> experiment results".
>
> It would also be nice to collect a histogram of the measures from each
> connection/session.  Thoughts on this?
>
> -Ted
>
>
> -- 
> Ted Bullock <tbullock at canada.com>
> http://www.comlore.com
> High Voltage Software Engineer
>

--
Mark Nottingham       mnot at yahoo-inc.com