From: Chris Mason <chris.mason@oracle.com>
To: "krzf83@gmail.com" <krzf83@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: checkpoints to often
Date: Thu, 31 Mar 2011 10:35:51 -0400 [thread overview]
Message-ID: <1301582070-sup-5170@think> (raw)
In-Reply-To: <AANLkTinr4G=F6msPF=oVDrCU1uz2b-q8Do4f5htzP=ep@mail.gmail.com>
Excerpts from krzf83@gmail.com's message of 2011-03-31 10:30:51 -0400:
> There should be a way to make automatic checkpoints less frequent. On
> the busy ssd I have about 7 cp every second. If it were for example
> once every 5 minutes then one could set garbage removal every few
> days.
> Also garbage removal should have option to clean only if like 90% of
> drive is used. there is no need to remove cp-s when there is still
> many GB of space left.
I'm wondering how you're measuring check points? Btrfs does a
transaction commit ever 30 seconds, so finding 7 commits per second
seems strange.
We do have a lighter weight commit that is done for fsyncs, but this is
not a full check point.
There's no garbage removal in btrfs, we use reference counting instead
of a traditional log structured design.
-chris
prev parent reply other threads:[~2011-03-31 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 14:30 checkpoints to often krzf83@gmail.com
2011-03-31 14:35 ` Chris Mason [this message]
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=1301582070-sup-5170@think \
--to=chris.mason@oracle.com \
--cc=krzf83@gmail.com \
--cc=linux-btrfs@vger.kernel.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).