From owner-freebsd-hackers Mon Jun 25 5:25:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29]) by hub.freebsd.org (Postfix) with ESMTP id BC3B637B401 for ; Mon, 25 Jun 2001 05:25:35 -0700 (PDT) (envelope-from cmsedore@mailbox.syr.edu) Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1b) with SMTP id <0.001E6CA0@mailer.syr.edu>; Mon, 25 Jun 2001 8:25:35 -0400 Received: from localhost (cmsedore@localhost) by rodan.syr.edu (8.8.7/8.8.7) with ESMTP id IAA04130; Mon, 25 Jun 2001 08:25:34 -0400 (EDT) X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs Date: Mon, 25 Jun 2001 08:25:34 -0400 (EDT) From: Christopher Sedore X-Sender: cmsedore@rodan.syr.edu To: Richard Hodges Cc: Josh Osborne , freebsd-hackers@FreeBSD.ORG Subject: Re: question: aio / nbio / kqueue In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 22 Jun 2001, Richard Hodges wrote: > On Fri, 22 Jun 2001, Josh Osborne wrote: > > > On Friday, June 22, 2001, at 07:01 PM, E.B. Dreger wrote: > > > My question is, from a performance standpoint, in what situations are > > > these techniques most appropriate? > > > AIO is good when you are not receiving much data (or not receiving > > it very frequently), and presumably want very low latency. > > What if you want good performance with "moderate" disk IO, say ten > to twenty megabytes per second continuously? > > I tried AIO some months ago (4.1R or 4.2R), but had some trouble > with AIO, mainly that it seemed to lose track of half my files. > Not any particular files, it seemed that at any moment it would > just pick ten or so (out of maybe 20-25 files) to ignore at any > given time. > I've done this at the 3-6 MB/sec continous (peaks at 10MB+/sec) range with good success with aio, both the network and disk functions. Never had trouble with it losing track of files (not sure what you mean here). If you didn't tweak some of the default sysctl settings, you may have bumped limits that caused unexpected behaviour (though you should have gotten error returns to let you know). -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message