From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de ([212.227.126.130]:62239 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755557AbcCDEh5 (ORCPT ); Thu, 3 Mar 2016 23:37:57 -0500 Message-ID: <56D9111F.5000109@vlnb.net> Date: Thu, 03 Mar 2016 20:37:51 -0800 From: Vladislav Bolkhovitin MIME-Version: 1.0 Subject: Re: Fio high IOPS measurement mistake References: <56D525E1.6010407@vlnb.net> <56D66B1C.6050506@vlnb.net> <56D7A97F.9080800@vlnb.net> In-Reply-To: Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 7bit Sender: fio-owner@vger.kernel.org List-Id: fio@vger.kernel.org To: Sitsofe Wheeler Cc: "fio@vger.kernel.org" Sitsofe Wheeler wrote on 03/02/2016 11:10 PM: > On 3 March 2016 at 03:03, Vladislav Bolkhovitin wrote: >> For those who asked about perf profiling, it remained the same as before with the CPU >> consumption is all about timekeeping and memset: >> >> - 55.74% fio fio [.] clock_thread_fn >> clock_thread_fn > > Perhaps this is what is already included above but could you use the > -g option on perf to collect it into a call-graph and post the top > results? My trace was for -g perf option. All entries marked by '-' were expanded. Thanks, Vlad