[HDFS-12277] NNThroughputBenchmark should use cumulativeTime to calculate ops per second.

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Not A Bug
• Component/s: benchmarks, tools
• Target Version/s: 3.0.0-beta1
• Assignee: Michael Han
• Reporter: Michael Han
• Created: 08/Aug/17 19:10
• Updated: 14/Aug/17 20:42
• Resolved: 14/Aug/17 20:42

Description

NNThroughputBenchmark$getOpsPerSecond is using elapsedTime to calculate ops per second. elapsedTime is the time used to measure the time from the start to the finish of the benchmark main thread, and it's also the total execution time of the single slowest benchmark worker thread. To measure ops per second, we should use the total execution time of all worker threads, which is cumulativeTime. Otherwise, we could get bogus result, e.g. given same load, the more client threads we have (controlled by -threads), the larger ops per second the number would be, with the same NN and its server side configurations.