From owner-freebsd-arch Mon Feb 10 2: 1:48 2003 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80AAD37B401 for ; Mon, 10 Feb 2003 02:01:47 -0800 (PST) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id A141943F3F for ; Mon, 10 Feb 2003 02:01:46 -0800 (PST) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.6/8.12.6) with ESMTP id h1AA1jqV037780; Mon, 10 Feb 2003 11:01:45 +0100 (CET) (envelope-from phk@phk.freebsd.dk) To: David Schultz Cc: arch@FreeBSD.ORG Subject: Re: Our lemming-syncer caught in the act. From: phk@phk.freebsd.dk In-Reply-To: Your message of "Mon, 10 Feb 2003 01:50:40 PST." <20030210095040.GB5515@HAL9000.homeunix.com> Date: Mon, 10 Feb 2003 11:01:45 +0100 Message-ID: <37779.1044871305@critter.freebsd.dk> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20030210095040.GB5515@HAL9000.homeunix.com>, David Schultz writes: >Thus spake phk@phk.freebsd.dk : >> Yes, it makes a lot of sense. There is no point in batching up >> writes to the point of showing 200 requests off at once then >> wait 30 seconds, then do it again etc etc. >> >> We can and need to do better than that. > >It sounds like you're describing the old syncer. The new one >still shoves groups of buffers out at once, but on a file-by-file >basis rather than globally every 30 seconds. The plot is a short segment of a trace I made on a -current box yesterday and it shows actual performance of our current syncer(s). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message