From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Migrate to bcache: A few questions
Date: Wed, 1 Jan 2014 10:06:07 +0000 (UTC) [thread overview]
Message-ID: <pan$5d9a6$76e24cb6$d9958291$8c757ede@cox.net> (raw)
In-Reply-To: 52C1990D.9060704@gmail.com
Austin S Hemmelgarn posted on Mon, 30 Dec 2013 11:02:21 -0500 as
excerpted:
> I've actually tried a simmilar configuration myself a couple of times
> (also using Gentoo in-fact), and I can tell you from experience that
> unless things have changed greatly since kernel 3.12.1, it really isn't
> worth the headaches.
Basically what I posted, but "now with added real experience!" (TM) =:^)
> As an alternative to using bcache, you might try something simmilar to
> the following:
> 64G SSD with /boot, /, and /usr Other HDD with /var, /usr/portage,
> /usr/src, and /home tmpfs or ramdisk for /tmp and /var/tmp
> This is essentially what I use now, and I have found that it
> significantly improves system performance.
Again, very similar to my own recommendation. Nice to see others saying
the same thing. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-01-01 10:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 21:11 Migrate to bcache: A few questions Kai Krakow
2013-12-30 1:03 ` Chris Murphy
2013-12-30 1:22 ` Kai Krakow
2013-12-30 3:48 ` Chris Murphy
2013-12-30 9:01 ` Marc MERLIN
2013-12-31 0:31 ` Kai Krakow
2013-12-30 6:24 ` Duncan
2013-12-31 3:13 ` Kai Krakow
2013-12-30 16:02 ` Austin S Hemmelgarn
2014-01-01 10:06 ` Duncan [this message]
2014-01-01 20:12 ` Austin S Hemmelgarn
2014-01-02 8:49 ` Duncan
2014-01-02 12:36 ` Austin S Hemmelgarn
2014-01-03 0:09 ` Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='pan$5d9a6$76e24cb6$d9958291$8c757ede@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).