From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753536Ab1HCPpr (ORCPT ); Wed, 3 Aug 2011 11:45:47 -0400 Received: from mx1.redhat.com ([209.132.183.28]:13300 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752614Ab1HCPpl (ORCPT ); Wed, 3 Aug 2011 11:45:41 -0400 Date: Wed, 3 Aug 2011 11:45:33 -0400 From: Vivek Goyal To: Gui Jianfeng Cc: Shaohua Li , Jens Axboe , linux-kernel@vger.kernel.org Subject: Re: fio posixaio performance problem Message-ID: <20110803154533.GB32385@redhat.com> References: <4E38C314.8070305@cn.fujitsu.com> <4E3902C7.9050907@cn.fujitsu.com> <4E391986.90108@cn.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4E391986.90108@cn.fujitsu.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 03, 2011 at 05:48:54PM +0800, Gui Jianfeng wrote: > On 2011-8-3 16:22, Shaohua Li wrote: > > 2011/8/3 Gui Jianfeng : > >> On 2011-8-3 15:38, Shaohua Li wrote: > >>> 2011/8/3 Gui Jianfeng : > >>>> Hi, > >>>> > >>>> I ran a fio test to simulate qemu-kvm io behaviour. > >>>> When job number is greater than 2, IO performance is > >>>> really bad. > >>>> > >>>> 1 thread: aggrb=15,129KB/s > >>>> 4 thread: aggrb=1,049KB/s > >>>> > >>>> Kernel: lastest upstream > >>>> > >>>> Any idea? > >>>> > >>>> --- > >>>> [global] > >>>> runtime=30 > >>>> time_based=1 > >>>> size=1G > >>>> group_reporting=1 > >>>> ioengine=posixaio > >>>> exec_prerun='echo 3 > /proc/sys/vm/drop_caches' > >>>> thread=1 > >>>> > >>>> [kvmio-1] > >>>> description=kvmio-1 > >>>> numjobs=4 > >>>> rw=write > >>>> bs=4k > >>>> direct=1 > >>>> filename=/mnt/sda4/1G.img > >>> Hmm, the test runs always about 15M/s at my side regardless how many threads. > >> > >> CFQ? > > yes. > > > >> what's the slice_idle value? > > default value. I didn't change it. > > Hmm, I use a sata disk, and can reproduce this bug every time... Do you have blktrace of run with 4 jobs? Thanks Vivek