filebench - Man Page
interprets WML script and generates appropriate filesystem workload
filebench [-f <filename>] [-h]
Filebench is a file system and storage benchmark that allows to generate a large variety of workloads. Unlike typical benchmarks it is very flexible and allows to minutely specify (any) applications' behaviour using extensive Workload Model Language (WML). Filebench uses loadable workload personalities to allow easy emulation of complex applications (e.g., mail, web, file, and database servers). Filebench is quick to set up and easy to use compared to deploying real applications. It is also a handy tool for micro-benchmarking.
Filebench includes many features to facilitate file system benchmarking:
- Multiple workload types support via loadable personalities
- Ships with more than 40 pre-defined personalities, including the one that describe mail, web, file, and database servers behaviour
- Easy to add new personalities using reach Workload Model Language (WML)
- Multi-process and multi-thread workload support
- Configurable directory hierarchies with depth, width, and file sizes set to given statistical distributions
- Support of asynchronous I/O and process synchronization primitives
- Integrated statistics for throughput, latency, and CPU cycle counts per system call
- -f <filename>
use specified file as an input instead of stdin
Display verbose help
- Run filebench interactively:
- $ filebench
Start filebench interactive shell, filebench prompt will appear after that.
- filebench> load fileserver
Load fileserver personality using load command.
- filebench> set $dir=/mnt
After personality is loaded, tunables of the workload personality can be set. Here we change the benchmark directory to /mnt where the file system we want to benchmark is presumably mounted.
- filebench> run 60
Start workload for 60 seconds. After 60 seconds of the run the statistics is printed and Filebench exits.
- Run filebench non-interactively:
- filebench -f /usr/share/filebench/workloads/fileserver.f
Run filebench non-interactively, however, you need to add 'run <time>' to the end of the workload personality file before calling filebench.
0 if OK,
1 if workload file is not found.