From owner-freebsd-questions@FreeBSD.ORG Fri Dec 5 15:48:25 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 73C4FFFB for ; Fri, 5 Dec 2014 15:48:25 +0000 (UTC) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id 4ACFBD6C for ; Fri, 5 Dec 2014 15:48:25 +0000 (UTC) Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.41]) by be-well.ilk.org (Postfix) with ESMTP id 38A9833C1D for ; Fri, 5 Dec 2014 10:48:19 -0500 (EST) Received: by lowell-desk.lan (Postfix, from userid 1147) id 70E6B39813; Fri, 5 Dec 2014 10:48:17 -0500 (EST) From: Lowell Gilbert To: freebsd-questions@freebsd.org Subject: Re: FreeBSD working from RAM (MFSROOT) as a Workstation. References: <1417734458.1772.1.camel@zoho.com> <447fy665uf.fsf@be-well.ilk.org> <20141205131229.5ebd96d2@gumby.homeunix.com> <4461dqf6ui.fsf@lowell-desk.lan> Reply-To: freebsd-questions@freebsd.org Date: Fri, 05 Dec 2014 10:48:17 -0500 In-Reply-To: <4461dqf6ui.fsf@lowell-desk.lan> (Lowell Gilbert's message of "Fri, 05 Dec 2014 10:34:45 -0500") Message-ID: <44y4qmdrni.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2014 15:48:25 -0000 Oops. Sent that last message before I meant to. One more comment. RW writes: > An alternative might be to do a conventional boot and then kick-off a > background script that pre-caches as much of the SSD as will fit in the > remaining free memory. I'd try this first because it's a lot less > trouble and will give a reasonable indication of how much thing can be > speeded-up (at least until the cache is driven-out by something else). I used to do something like this back when disks were slower. I can't remember why I stopped. Rather than boot time, it started a few seconds after I started an X session. I recall I spent a little time tuning it to minimize CPU consumption, but nothing all that tricky. Maybe I'll dig it out of my backups and see if it's a noticeable help today.