Hi Drew,
> The goal is to make it easy for other file system clients, such as
> nfsv3, to be added to filebench. The will supply their own routines to
> implement the I/O functions, as well as custom asynchronous flowops.
>
> See it all at:
>
> http://cr.opensolaris.org/~dreww/localfs_plugin/
In preparation for developing a set of file system plug-in modules, this
change set has been created which introduces an I/O functions vector
which both flowop_library.c and fileset.c use to make file system calls.
It creates a new header file, fsplug.h which defines the vector and
macros for a
Stefan Parvu wrote:
>
>> For papers and books on this, start with the
>> Teamquest site and view their webinar
>> http://teamquest.com/resources/webinars/display/30/index.htm
>> and if you don't mind math, follow up with Neil
>> Gunther's site, http://www.perfdynamics.com/
>>
>
> Right. I have
Hi David,
> The classic tools for doing capacity planning measure
> operation/transaction rate and time taken, rather
> than resource usage.
>
> Once you've *done* the planning, then you correlate
> that with the amount of resources you used and use
> that to predict when you need to add more r
