Add ramp_time option
Sometimes it's useful to let a job settle for a little while
before taking any measurements on latency and throughput, since
the initial rate on eg a write workload may be much higher than
the longer sustained rate.
So add a ramp_time option that allows the user to specify a lead
ramp time that must have passed before fio takes any performance
numbers into account.
Suggested by "Jenkins, Lee" <Lee.Jenkins@hp.com>
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
diff --git a/fio.h b/fio.h
index 22aaf34..a0c1109 100644
--- a/fio.h
+++ b/fio.h
@@ -473,6 +473,7 @@
unsigned int fsync_blocks;
unsigned int start_delay;
unsigned long long timeout;
+ unsigned long long ramp_time;
unsigned int overwrite;
unsigned int bw_avg_time;
unsigned int loops;
@@ -609,6 +610,7 @@
struct timeval rw_end[2];
struct timeval last_issue;
unsigned int rw_end_set[2];
+ unsigned int ramp_time_over;
/*
* read/write mixed workload state
@@ -817,6 +819,7 @@
extern void fill_start_time(struct timeval *);
extern void fio_gettime(struct timeval *, void *);
extern void set_genesis_time(void);
+extern int ramp_time_over(struct thread_data *);
/*
* Init/option functions