public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roesch <shr@fb.com>
To: Nikolay Borisov <nborisov@suse.com>,
	<linux-btrfs@vger.kernel.org>, <kernel-team@fb.com>
Subject: Re: [PATCH v4 4/4] btrfs: increase metadata alloc size to 5GB for volumes > 50GB
Date: Tue, 9 Nov 2021 13:19:55 -0800	[thread overview]
Message-ID: <caf2d757-8a5c-7665-56ca-bf05346d00ce@fb.com> (raw)
In-Reply-To: <443789f1-1b62-80e6-a88d-73e1fd11233b@suse.com>



On 11/5/21 3:11 AM, Nikolay Borisov wrote:
> 
> 
> On 29.10.21 г. 21:39, Stefan Roesch wrote:
>> This increases the metadata default allocation size from 1GB to 5GB for
>> volumes with a size greater than 50GB.
> 
> Imo such a change would warrant more data about why it's ok. Clearly
> there is some internal facebook workload which benefits from this,
> however this doesn't automatically mean it will be beneficial for the
> wider user base. Also your cover letter doesn't contain any more
> specifics about the particular workload. Isn't 5g a bit too steep,
> perhaps 2 is larger and yet more conservative?
>

I understand that this change is getting some questions and a more conservative
value might need to be chosen. Let's wait until all the reviews are in and
then settle on a compromise. 
 
> 
>>
>> Signed-off-by: Stefan Roesch <shr@fb.com>
>> ---
>>  fs/btrfs/space-info.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/btrfs/space-info.c b/fs/btrfs/space-info.c
>> index 7370c152ce8a..44507262c515 100644
>> --- a/fs/btrfs/space-info.c
>> +++ b/fs/btrfs/space-info.c
>> @@ -195,7 +195,7 @@ static u64 compute_chunk_size_regular(struct btrfs_fs_info *info, u64 flags)
>>  
>>  	/* Handle BTRFS_BLOCK_GROUP_METADATA */
>>  	if (info->fs_devices->total_rw_bytes > 50ULL * SZ_1G)
>> -		return SZ_1G;
>> +		return 5ULL * SZ_1G;
>>  
>>  	return SZ_256M;
>>  }
>>

  reply	other threads:[~2021-11-09 21:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29 18:39 [PATCH v4 0/4] btrfs: sysfs: set / query btrfs chunk size Stefan Roesch
2021-10-29 18:39 ` [PATCH v4 1/4] btrfs: store chunk size in space-info struct Stefan Roesch
2021-11-05  8:52   ` Nikolay Borisov
2021-11-09 19:44     ` Stefan Roesch
2021-10-29 18:39 ` [PATCH v4 2/4] btrfs: expose chunk size in sysfs Stefan Roesch
2021-11-05  9:27   ` Nikolay Borisov
2021-11-09  1:57     ` Stefan Roesch
2021-11-09  6:36       ` Nikolay Borisov
2021-10-29 18:39 ` [PATCH v4 3/4] btrfs: add force_chunk_alloc sysfs entry to force allocation Stefan Roesch
2021-11-05 10:04   ` Nikolay Borisov
2021-11-09  1:09     ` Stefan Roesch
2021-10-29 18:39 ` [PATCH v4 4/4] btrfs: increase metadata alloc size to 5GB for volumes > 50GB Stefan Roesch
2021-11-05 10:11   ` Nikolay Borisov
2021-11-09 21:19     ` Stefan Roesch [this message]
2021-11-02 16:15 ` [PATCH v4 0/4] btrfs: sysfs: set / query btrfs chunk size Josef Bacik

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=caf2d757-8a5c-7665-56ca-bf05346d00ce@fb.com \
    --to=shr@fb.com \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.com \
    /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