From: Alex Elsayed <eternaleye-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: bcache and SSD over provisioning
Date: Wed, 13 Nov 2013 14:30:44 -0800 [thread overview]
Message-ID: <l60uia$5ua$1@ger.gmane.org> (raw)
In-Reply-To: 5283D85B.10904@gmail.com
Francis Moreau wrote:
> Hello Matthew,
>
> Le 13/11/2013 15:13, Matthew Patton a écrit :
>> On Wed, 13 Nov 2013 03:42:54 -0500, Francis Moreau
>> <francis.moro-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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?
>>
>
> That's indeed not really required: my system is for a desktop usage.
>
>>> - Should I create 2 partitions with one left emtpy and whose size is
>>> roughly 7% of the device size ?
>>
>> Your SSD already has 7% overprovisioning. For best sustained and
>> consistent write performance you'll want to bump it to 25-30%. Yes you
>> just need to partition/LVM down to the desired size.
>
> Hmm, I don't see what makes you think that my SSD has already 7%
> overprovisioning ? Actually I don't think it's the case.
>
> Thanks for your help.
Because the raw flash chips are only available in power-of-two sizes. The
available storage the controller allows access to is 120GB, and it's
reserved 8GB for overprovisioning if I'm looking at the right model.
next prev parent reply other threads:[~2013-11-13 22:30 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
2013-11-13 20:12 ` Paul B. Henson
2013-11-13 19:51 ` Francis Moreau
2013-11-13 22:30 ` Alex Elsayed [this message]
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='l60uia$5ua$1@ger.gmane.org' \
--to=eternaleye-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@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;
as well as URLs for NNTP newsgroup(s).