Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[benchmarks] Add a container for FileBench #20

Open
rouvoy opened this issue Apr 6, 2016 · 0 comments
Open

[benchmarks] Add a container for FileBench #20

rouvoy opened this issue Apr 6, 2016 · 0 comments

Comments

@rouvoy
Copy link
Member

rouvoy commented Apr 6, 2016

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.

Features

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
  • Tested on Linux, FreeBSD, and Solaris platforms (should work for any POSIX-compliant Operating System)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant