From: Brad Campbell <brad-+nnirC7rrGZibQn6LdNjmg@public.gmane.org>
To: Matthew Patton <pattonme-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>,
Vasiliy Tolstov
<v.tolstov-+9FY0jupvH6HXe+LvDLADg@public.gmane.org>,
linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: full ssd for bcache or part?
Date: Thu, 24 Oct 2013 10:24:56 +0800 [thread overview]
Message-ID: <526884F8.4080000@fnarfbargle.com> (raw)
In-Reply-To: <f46b2a85-6116-4dac-8acd-03007110cf4b-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
On 10/24/2013 12:15 AM, Matthew Patton wrote:
> 25 to 30 percent reserve is strongly recommended for any write heavy workload. The performance improvement will blow your mind.
>
> A 240GB drive is a 256 with 7 percent reserve. Partition your device to 185 GB.
I thought (and maybe I'm wrong) that a good chunk of reserved space was
essential to allow the drive to efficiently manage its read-modify-write
cycles. It was my understanding that bcache was explicitly designed to
fill erase block sized chunks sequentially and discard them in whole
units, negating the requirement for the drive to actually perform RMW
cycles and therefore negating the requirement for the extra free space.
Have I got it wrong?
Regards,
Brad
next prev parent reply other threads:[~2013-10-24 2:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 14:49 full ssd for bcache or part? Vasiliy Tolstov
[not found] ` <CACaajQscOOajT2A6MNpstALph8D=jqdvqifynYxxR4gTXrGTGQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-23 16:15 ` Matthew Patton
[not found] ` <f46b2a85-6116-4dac-8acd-03007110cf4b-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2013-10-23 16:55 ` Vasiliy Tolstov
2013-10-24 2:24 ` Brad Campbell [this message]
[not found] ` <526884F8.4080000-+nnirC7rrGZibQn6LdNjmg@public.gmane.org>
2013-10-24 3:40 ` matthew patton
[not found] ` <1382586002.46067.YahooMailNeo-XYahOdtEMNnuQS8rMknbopOW+3bF1jUfVpNB7YpNyf8@public.gmane.org>
2013-10-24 4:08 ` Brad Campbell
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=526884F8.4080000@fnarfbargle.com \
--to=brad-+nnirc7rrgzibqn6ldnjmg@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pattonme-/E1597aS9LQAvxtiuMwx3w@public.gmane.org \
--cc=v.tolstov-+9FY0jupvH6HXe+LvDLADg@public.gmane.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