'trans_size' description from header: "size of the write/read to perform"
But really 'object_size' is used in write/read operations. 'trans_size' is used
only in ObjBencher::status_printer for calc current and average bandwidth.
As result - bad statistics in case 'trans_size' and and 'object_size' are different.
Signed-off-by: Dmitry Yatsushkevich <dyatsushkevich@mirantis.com>
}
if (cycleSinceChange)
bandwidth = (double)(data.finished - previous_writes)
- * (data.trans_size)
+ * (data.object_size)
/ (1024*1024)
/ cycleSinceChange;
else
data.history.iops.push_back(iops);
}
- double avg_bandwidth = (double) (data.trans_size) * (data.finished)
+ double avg_bandwidth = (double) (data.object_size) * (data.finished)
/ (double)(cur_time - data.start_time) / (1024*1024);
if (previous_writes != data.finished) {
previous_writes = data.finished;
lock.Lock();
data.done = false;
data.object_size = object_size;
- data.trans_size = op_size;
data.in_flight = 0;
data.started = 0;
data.finished = num_objects;
struct bench_data {
bool done; //is the benchmark is done
int object_size; //the size of the objects
- int trans_size; //size of the write/read to perform
// same as object_size for write tests
int in_flight; //number of reads/writes being waited on
int started;