From owner-freebsd-isp Thu Feb 18 15:42:17 1999 Delivered-To: freebsd-isp@freebsd.org Received: from aniwa.sky (p9-max8.wlg.ihug.co.nz [209.79.142.201]) by hub.freebsd.org (Postfix) with ESMTP id 5BC32119D2 for ; Thu, 18 Feb 1999 15:42:09 -0800 (PST) (envelope-from andrew@squiz.co.nz) Received: from aniwa.sky (localhost [127.0.0.1]) by aniwa.sky (8.9.1a/8.9.1) with ESMTP id XAA22473 for ; Thu, 18 Feb 1999 23:42:06 GMT Message-Id: <199902182342.XAA22473@aniwa.sky> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-isp@FreeBSD.ORG Subject: file locking Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Feb 1999 12:42:06 +1300 From: Andrew McNaughton Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm doing some tuning of a perl script which serves up web banners. Disk IO is the critical resource, and the way the script is structured means that multiple instances wind up waiting on each other's file locks. Can anyone tell me what level of disk overhead is caused by checking repeatedly for the presence of an flock, or a file. Is this significant, or does it just get negated by cache? Is there an advantage to flock over lock files or vice versa? Andrew McNaughton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message