From: "Chris Murphy" <lists@colorremedies.com>
To: "Qu Wenruo" <quwenruo.btrfs@gmx.com>, fdavidl073rnovn@tutanota.com
Cc: "Qu WenRuo" <wqu@suse.com>, "Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: Deleting large amounts of data causes system freeze due to OOM.
Date: Sat, 14 Oct 2023 15:09:56 -0400 [thread overview]
Message-ID: <7dd58d68-3daf-4dd5-b6b7-e3ee0e160f68@app.fastmail.com> (raw)
In-Reply-To: <7bcaeca0-641a-43e8-8ffb-1f729e5e327d@gmx.com>
On Fri, Oct 13, 2023, at 6:32 PM, Qu Wenruo wrote:
> On 2023/10/14 08:58, fdavidl073rnovn@tutanota.com wrote:
>> Is there anything else I can do to make sure this is addressed at some point? I would like to eventually be able to re-enable compression as it was saving me several terabytes.
>
> I believe Filipe is working on improving the extent map code recently.
> You may want to test his patchset when it comes out.
>
> Otherwise you may need to keep away from compression for now.
Is the cost of tracking extents reduced at all by increasing leaf/node size? The number of extents is the same, so that cost wouldn't be reduced - and maybe that's the bulk of the problem. But if it's also related to the cost of having so many leaves, maybe it would help?
next prev parent reply other threads:[~2023-10-14 19:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 2:28 Deleting large amounts of data causes system freeze due to OOM fdavidl073rnovn
2023-09-13 5:55 ` Qu Wenruo
2023-09-14 3:38 ` fdavidl073rnovn
2023-09-14 5:12 ` Qu Wenruo
2023-09-14 23:08 ` fdavidl073rnovn
2023-09-27 1:46 ` fdavidl073rnovn
2023-09-27 4:53 ` Qu Wenruo
2023-09-28 23:32 ` fdavidl073rnovn
2023-09-29 1:01 ` Qu Wenruo
2023-10-13 22:28 ` fdavidl073rnovn
2023-10-13 22:32 ` Qu Wenruo
2023-10-14 19:09 ` Chris Murphy [this message]
2023-10-14 22:10 ` Qu Wenruo
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=7dd58d68-3daf-4dd5-b6b7-e3ee0e160f68@app.fastmail.com \
--to=lists@colorremedies.com \
--cc=fdavidl073rnovn@tutanota.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@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;
as well as URLs for NNTP newsgroup(s).