The Faban driver framework is a framework is a Java™ platform-based framework that allows developers to easily define new benchmarks using the Java Programming Language. It makes use of the Java 2 Standard Edition (J2SE) 5.0 features, primarily annotations as documented in
to ease benchmark development. The benchmark developer will only need to focus on the benchmark driver logic. The timing and selection of the operations, including recording of the metrics is handled by the driver framework.
The goal of the Faban driver framework is to allow for extremely easy and efficient creation of new benchmark drivers for N-Tier benchmarks driven from network-connected driver systems. New and added operations should be no more complex than a script, which, in its very basic form can be captured. Specifications for the driver is given in descriptive form. The driver framework supports the following features:
The System Under Test (SUT) comprises all components being tested and varies from benchmark to benchmark. The driver framework and the driver is usually not part of the SUT. Some non client-server benchmarks can however not differentiate between the SUT and the driver making the driver implicitly part of the SUT.
An Operation is a single unit of work executed by the user or the driver and timed, and managed by the driver.
Mix defines how operations are executed by a simulated user or
An Operation Cycle
defines the timing characteristics from one operation to the next.
A Metric is the resulting data of the operations collected over the steady state time of the benchmark operation.
Cycle Time defines the elapsed time between the begin of the previous operation to the begin of the current operation.
Think Time defines the elapsed time between the end of the previous operation to the begin of the current operation.
The Critical Section defines the portion of an operation in which the response time is measured.
Data Preparation Section defines the portion of an operation before the critical section where the data gets prepared.
Section defines the portion of an operation after the critical
section where the results get validated.