From owner-freebsd-hackers Sun Jul 30 9:58:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 1D93C37B673; Sun, 30 Jul 2000 09:58:48 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id MAA86668; Sun, 30 Jul 2000 12:58:40 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Sun, 30 Jul 2000 12:58:39 -0400 (EDT) From: Adam To: Doug Barton Cc: freebsd-hackers@FreeBSD.ORG, dillon@FreeBSD.ORG Subject: Re: /tmp on a ramdisk? In-Reply-To: <398223FF.17B737A7@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Jul 2000, Doug Barton wrote: >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 I thought that was MFS only and that MD took care of that issue? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message