From owner-freebsd-hackers Fri Jul 28 17:23:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dt052n3e.san.rr.com (dt052n3e.san.rr.com [204.210.33.62]) by hub.freebsd.org (Postfix) with ESMTP id A8F1637C2E0 for ; Fri, 28 Jul 2000 17:23:29 -0700 (PDT) (envelope-from DougB@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt052n3e.san.rr.com (8.9.3/8.9.3) with ESMTP id RAA12156; Fri, 28 Jul 2000 17:23:27 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <398223FF.17B737A7@gorean.org> Date: Fri, 28 Jul 2000 17:23:27 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Ted Sikora Cc: "freebsd-hackers@FreeBSD.ORG" Subject: Re: /tmp on a ramdisk? References: <39821108.CD43006A@home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Sikora wrote: > > A while ago several people suggested using /tmp on a ramdisk along with > softupdates. Right now I am running several production servers with > 4.1-STABLE with softupdates. I'm really happy with the performance. What > benefits would I realize using /tmp on a ramdisk? CW on this is varied, but the current trend is that /tmp on a md is just a waste of ram, since (basically) everything in /tmp is in ram twice. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message