httperf roadmap

[Ted Bullock]

FYI,

I'm actively back into developing for httperf. I've got some business
rationale for this on my own end which is my impetus for action, but
that is really here nor there.

For 0.9.1:

Data export - key=value and csv
new --url option

Compatibility will be verified against:
Solaris >= 8
OpenBSD >=4.7
FreeBSD >= 4.11
Debian >= 5
CentOS >= 5.5

For 1.0:

libevent - Full event loop
(This is enough work all on its own so this will be the only major change)

For 1.1:

Refactor to libhttperf with workload generators creating distinct
binaries with distinct "options", rather than one all singing all
dancing binary with options and parameters which change their role
depending on workload generator context (sheesh).

--
Ted Bullock <tbul...@comlore.com>

[Martin Arlitt]

hi Ted

 

its good to hear that you will have some time to extend the development of httperf.

 

regarding 0.9.1, can you add in a few more things? I'm thinking functionality that has already been developed in various places (e.g., Mark, Diwakar, myself, etc.).

 

regarding 1.1, I'm not quite sure what you have in mind. while there may be a lot of options, most are not needed at the same time. Those that are can be included in a script to simplify use. Why not just create a few wrapper scripts to accomplish this?

 

thanks

Martin

[Ted Bullock]

On Thu, Feb 10, 2011 at 6:03 AM, Martin Arlitt
<martin...@gmail.com> wrote:
> regarding 0.9.1, can you add in a few more things? I'm thinking
> functionality that has already been developed in various places (e.g., Mark,
> Diwakar, myself, etc.).

Sure, if you have patches, mail me and I'll make sure they are nicely
integrated.

> regarding 1.1, I'm not quite sure what you have in mind. while there may be
> a lot of options, most are not needed at the same time. Those that are can
> be included in a script to simplify use. Why not just create a few wrapper
> scripts to accomplish this?

I'll explain what I have in mind here in a follow up message.

--
Ted Bullock <tbul...@comlore.com>

[Ted Bullock]

On Thu, Feb 10, 2011 at 6:03 AM, Martin Arlitt <martin...@gmail.com> wrote:

> hi Ted
>
> its good to hear that you will have some time to extend the development of
> httperf.
>
> regarding 0.9.1, can you add in a few more things? I'm thinking
> functionality that has already been developed in various places (e.g., Mark,
> Diwakar, myself, etc.).

What do you have in mind?

--
Ted Bullock <tbul...@comlore.com>

[Martin Arlitt]

Hi Ted

I have some extensions and fixes, I'll send the code in the next day or so.

I recall Mark saying he had one or more extensions too. So does Diwakar, I believe. I'll let them elaborate.

Thanks
Martin

Sent from my iPhone

[Martin Arlitt]

hi Ted

here is the source with my implementation of IPv6 support, and a fix for the Connection: close bug. Note I had to rename the gzipped tar file because Gmail wouldn't mail the original.

I may send some additional changes too, but first I need to check with my former colleague who wrote one of them.

thanks
Martin

[Martin Arlitt]

hi Ted

here is an snapshot of a modified 0.8 httperf. See README.changes for description of some of the added features (note you likely addressed all of the bugs in 0.8.1 back in 2007).

the original version of the VARIABLE_RATE option was implemented by Srinivas Ramanathan while he was an HP Labs employee. I checked with Srinivas this morning, he is fine with contributing it to httperf.

some of the other options may not be that useful, so you do not need to include them. However, a few people (myself included) have made use of the various options to use multiple source addresses when generating a load with httperf. Of course, it requires that the client support those addresses...

thanks
Martin

[Dave Viner]

Also, feel free to include the patch I sent a few months back to embed HTTP headers in the data file.

Thanks

Dave Viner