Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261979AbVBAKuQ (ORCPT ); Tue, 1 Feb 2005 05:50:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261985AbVBAKuQ (ORCPT ); Tue, 1 Feb 2005 05:50:16 -0500 Received: from ns.virtualhost.dk ([195.184.98.160]:36241 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id S261979AbVBAKty (ORCPT ); Tue, 1 Feb 2005 05:49:54 -0500 Date: Tue, 1 Feb 2005 11:49:49 +0100 From: Jens Axboe To: "Catalin(ux aka Dino) BOIE" Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org Subject: Re: Strange vmstat output. 2.6.10 Scheduler? Message-ID: <20050201104949.GM4137@suse.de> References: <20050201102638.GJ4137@suse.de> <20050201104214.GK4137@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1070 Lines: 34 On Tue, Feb 01 2005, Catalin(ux aka Dino) BOIE wrote: > >Well then that is why, the writes are taking quite a while to reach the > >platter. Nothing is wrong, the drive is just slow :-) > > > >-- > >Jens Axboe > > I don't know what to say because sometimes works really good. > bi=20000. The vmstat you showed had bi and bo at the same time, so it's not so surprising if bi often suffers if it is seeking all over the map to write out the big chunk submitted. How does it look with write cache enabled? > I'm fighting with this problem for 1 month now and I realy tried to > resolve the problem. If postgres uses fsync() properly, you should be safe with write cache enabled. > P.S. I tried also with cfq and see no improvement. Not surprising, there's not much the io scheduler can do for you here. -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/