Filebench [PSARC/2007/448 FastTrack timeout 08/16/2007]

[eric kustarz]

On Aug 2, 2007, at 12:24 PM, James Carlson wrote:

> Matthew Ahrens writes:
>>         This project delivers the following executable perl script:
>>         /usr/benchmarks/filebench/filebench
>
> Not mentioned here is that this seems to establish a precedent for a
> directory called /usr/benchmarks, with subdirectories for each
> benchmark.

Correct.

>
> It seems to be akin to /usr/demo/ (is that right?), but the semantics
> are somewhat unclear, as it seems unlikely that anyone would deliver
> more than handful of executables in any directory, and likely that
> it's just a single file per directory.
>
> Are there other things that might fit here?  Future plans?

Yep.  One thing we're definitely planning on adding to /usr/ 
benchmarks is libMicro.

Bart mentioned that he would like more than just a single executable  
in the libmicro directory.  Something like:
/usr/benchmarks/libmicro/libmicro (executable)
/usr/benchmarks/libmicro/README
/usr/benchmarks/libmicro/libmicro.tar.gz

>
> An update to filesystem(5) to describe this new hierarchy would be
> helpful.

Ah yes, thanks for pointing that out.

>
>> User Commands                                             filebench 
>> (1)
>>
>> NAME
>>      filebench - framework of workloads to measure and compare
>>      filesystem performance
>
> Nit: since it's on a non-default path, I think this man page should
> include the full path.

Sure thing.

>
> Would it make sense to have a new subsection (say, 1BENCH) to collect
> these man pages together?  Otherwise, I think it seems a little odd to
> have things in section 1 that aren't going directly into /usr/bin.

Whatever the ARC/manpage experts think is the right way is a-ok with me.

eric