From: Francis Moreau <francis.moro-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Adam Berkan <aberkan-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
Matthew Patton <pattonme-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: "linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: bcache and SSD over provisioning
Date: Wed, 13 Nov 2013 20:54:38 +0100 [thread overview]
Message-ID: <5283D8FE.5000908@gmail.com> (raw)
In-Reply-To: <CAHYUNGZAp8_LNqTJ6ufnVjLEnK-8cn0SKYgtH+YpVw_ki2+ONQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Le 13/11/2013 19:23, Adam Berkan a écrit :
> On Wed, Nov 13, 2013 at 6:13 AM, Matthew Patton <pattonme-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> wrote:
>> On Wed, 13 Nov 2013 03:42:54 -0500, Francis Moreau <francis.moro@gmail.com>
>> wrote:
>>
>>> First I'd like to know if over-provisioning is still needed when
>>> bcache is used ?
>>
>>
>> it's needed for any decent, sustained write load if you don't want
>> performance to crash thru the floor. But it doesn't sound like this is your
>> use case. Are you sustaining 5000+ write IOPs?
>>
>>
>>> - Should I create 2 partitions with one left emtpy and whose size is
>>> roughly 7% of the device size ?
>>
> bcache has a pretty flash friendly write pattern, so you probably
> don't need a huge lot of empty space. The 7% might in fact be enough,
> but bumping it up to 10%-12% wouldn't hurt. I think the >25% numbers
> are more relevant for non-flash friendly writes (like random writes).
> In that case you definitely want lots of free space.
Thanks for your enlightment.
I'll probably go for 10%.
next prev parent reply other threads:[~2013-11-13 19:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 8:42 bcache and SSD over provisioning Francis Moreau
[not found] ` <CAC9WiBiuQ2zG6C9XJio-STz-ScnfzzYb+Rz23u6JW+vFni8PNA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-13 14:13 ` Matthew Patton
[not found] ` <op.w6hq4v0of3gqgg-r49W/1Cwd2cba4AQcYcrVKxOck334EZe@public.gmane.org>
2013-11-13 14:32 ` Zachary Palmer
[not found] ` <52838D74.6020502-J5qI5MFTcs8@public.gmane.org>
2013-11-13 14:42 ` Matthew Patton
[not found] ` <op.w6hshrv5f3gqgg-r49W/1Cwd2cba4AQcYcrVKxOck334EZe@public.gmane.org>
2013-11-13 15:17 ` Zachary Palmer
[not found] ` <5283981B.8090900-J5qI5MFTcs8@public.gmane.org>
2013-11-13 19:58 ` Francis Moreau
2013-11-13 18:23 ` Adam Berkan
[not found] ` <CAHYUNGZAp8_LNqTJ6ufnVjLEnK-8cn0SKYgtH+YpVw_ki2+ONQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-13 19:54 ` Francis Moreau [this message]
2013-11-13 20:12 ` Paul B. Henson
2013-11-13 19:51 ` Francis Moreau
2013-11-13 22:30 ` Alex Elsayed
2013-11-14 6:12 ` Francis Moreau
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=5283D8FE.5000908@gmail.com \
--to=francis.moro-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=aberkan-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pattonme-/E1597aS9LQAvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.