From owner-freebsd-current Thu Jun 22 12:28:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA21995 for current-outgoing; Thu, 22 Jun 1995 12:28:47 -0700 Received: from hutcs.cs.hut.fi (root@hutcs.cs.hut.fi [130.233.192.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA21985 for ; Thu, 22 Jun 1995 12:28:44 -0700 Received: from shadows.cs.hut.fi by hutcs.cs.hut.fi with SMTP id AA03550 (5.65c8/HUTCS-S 1.4 for ); Thu, 22 Jun 1995 22:28:24 +0300 From: Heikki Suonsivu Received: (hsu@localhost) by shadows.cs.hut.fi (8.6.10/8.6.10) id WAA26211; Thu, 22 Jun 1995 22:28:34 +0300 Date: Thu, 22 Jun 1995 22:28:34 +0300 Message-Id: <199506221928.WAA26211@shadows.cs.hut.fi> To: freebsd-current@freefall.cdrom.com Subject: Does -o async do anything? Organization: Helsinki University of Technology, Otaniemi, Finland Sender: current-owner@FreeBSD.org Precedence: bulk I needed to copy a news partition over to another disk, so I told mount -o async on those disks. There was no noticeable improvement in performance. Neither it seems to have any effect on a running news system, which should gain considerably on doing asyncronous writes. The hardware is a P90 with 4G seagate hawk, no load other than copy (ie. cpu is practically idle). On a similar linux system it was hard to tell whether it was tar tf or tar xvf running, so it would seem that FreeBSD -o async doesn't disable all synchronous writing, if anything at all? -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN