From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk1-f177.google.com ([209.85.222.177]:36511 "EHLO mail-qk1-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726681AbeJPCz6 (ORCPT ); Mon, 15 Oct 2018 22:55:58 -0400 Received: by mail-qk1-f177.google.com with SMTP id a85-v6so12550587qkg.3 for ; Mon, 15 Oct 2018 12:09:25 -0700 (PDT) From: Vincent Fu Subject: Re: JSON versus terse : latency_us : "2" References: Message-ID: <18e69925-71ad-c735-e65a-80dcb1728af1@gmail.com> Date: Mon, 15 Oct 2018 15:09:23 -0400 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: fio-owner@vger.kernel.org List-Id: fio@vger.kernel.org To: "fio@vger.kernel.org" On 10/11/2018 01:51 PM, smitha sunder wrote: >>>>From the JSON output : > "latency_us" : { > "2" : 11.500203, <---- > "4" : 40.336987, > "10" : 2.821762, > "20" : 0.121803, > "50" : 0.020300, > "100" : 0.000000, > "250" : 0.000000, > "500" : 0.000000, > "750" : 0.000000, > "1000" : 0.000000 > }, > > Terse output : > lat_2us 56.70% <--- > lat_4us 40.34% > lat_10us 2.82% > lat_20us 0.12% > lat_50us 0.02% > lat_100us 0.00% > lat_250us 0.00% > lat_500us 0.00% > lat_750us 0.00% > lat_1000us 0.00% This is because the terse output has no nanosecond latency values. So the terse lat_2us bucket includes everything below 2us. The JSON latency_us 2 bucket includes only the percentage from 1-2us. There should also be a "latency_ns" JSON object with the percentage distribution for latencies under 1us. If you add up all those along with the latency_us 2 value of 11.5, you should get 56.7%.