AnsweredAssumed Answered

MB/s * execution time does not match the data size

Question asked by feeblefakie on Feb 26, 2012
Latest reply on Feb 26, 2012 by feeblefakie
I ran a simple map-only job with sar traces. (sar output is not the same disk as the data for MR job.)
The input data is 75GB, MB/s from sar traces is 242 (MB/s) and the execution time is 377 (s).
I am wondering why MB/s * the execution time does not match the input data size.
(I put the input data with .z extension so that compression is disabled for the data.)
MapR reads any data other than the input data ?

Outcomes