From owner-freebsd-fs Sun Feb 17 8: 5:56 2002 Delivered-To: freebsd-fs@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id F10FC37B404 for ; Sun, 17 Feb 2002 08:05:51 -0800 (PST) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.12.2/2002020400) with ESMTP id g1HG5pj06186 for ; Sun, 17 Feb 2002 17:05:51 +0100 (CET) Received: from mail.cs.uni-sb.de (IDENT:KkLAvN4o5jkz25yM8GAHXLWlABSDYSrr@mail.cs.uni-sb.de [134.96.254.200]) by cs.uni-sb.de (8.12.1/2001121800) with ESMTP id g1HG5os09029 for ; Sun, 17 Feb 2002 17:05:50 +0100 (CET) Received: from wjpserver.cs.uni-sb.de (wjpserver.cs.uni-sb.de [134.96.247.42]) by mail.cs.uni-sb.de (8.12.2/2002011500) with ESMTP id g1HG5mO01379 for ; Sun, 17 Feb 2002 17:05:48 +0100 (CET) Received: (from schuerge@localhost) by wjpserver.cs.uni-sb.de (8.11.0/8.11.0/wjp-SVR4/1999052600) id g1HG5ml26850 for freebsd-fs@freebsd.org; Sun, 17 Feb 2002 17:05:48 +0100 (MET) From: Thomas Schuerger Message-Id: <200202171605.g1HG5ml26850@wjpserver.cs.uni-sb.de> Subject: New dir layout slow on full disks!? To: freebsd-fs@freebsd.org Date: Sun, 17 Feb 2002 17:05:48 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL57 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi! I'm using 4.5-RELEASE and am quite happy with the new directory layout stuff. It really speeds up file scans etc. a lot. But there can be serious performance loss: When a disk is nearly full (e.g. 98%, but still 1,6 GB free, values taken from "df"), creating files becomes very slow. I noticed this when I wanted to install a big port (e.g. kdebase2). The extraction of the .tar.gz archive took really long and made my system more or less unusable. tar took something like 90-99% system time for 3 minutes. I compared extracting the same archive in /tmp (slice 1,disk 1, 3% full) with tar compared to extracting it somewhere in /usr/ports/... (slice 2,disk 1, 98% full). The latter took 8 times as long and almost completely blocked my system (note that this is on the same disk but on a different slice). Both slices use soft-updates. It seems that looking for free nearby blocks in the new directory layout algorithms is really slow when there are few free blocks available. Is anyone else experiencing this? Greetings, Thomas. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message