linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Torbjørn <lists@skagestad.org>
To: Kai Krakow <hurikhan77+btrfs@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Is the checkpoint interval adjustable?
Date: Sat, 03 Aug 2013 19:37:32 +0200	[thread overview]
Message-ID: <51FD3FDC.803@skagestad.org> (raw)
In-Reply-To: <17rvca-hju.ln1@hurikhan.ath.cx>

On 08/03/2013 07:28 PM, Kai Krakow wrote:
> Mike Audia <mikey_a@gmx.com> schrieb:
>
>> I believe 30 sec is the default for the checkpoint interval.  Is this
>> adjustable? --
>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Just curious: What would be the benefit of increasing the checkpoint
> interval?
Laptops typically spin down disks to save power. If btrfs forces a write 
every 30 second, you have to spin it back up.

--
Torbjørn
>
> As far as I understood it would not decrease write load on the drives
> because it will only update a few pointers and probably increase the
> generation number...
>
> Greetings,
> Kai


  reply	other threads:[~2013-08-03 17:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31 20:02 Is the checkpoint interval adjustable? Mike Audia
2013-07-31 20:54 ` Zach Brown
2013-08-03 17:28 ` Kai Krakow
2013-08-03 17:37   ` Torbjørn [this message]
2013-08-04  0:58     ` Kai Krakow
  -- strict thread matches above, loose matches on Subject: below --
2013-07-31 22:10 Mike Audia
2013-07-31 22:56 ` Zach Brown
2013-08-01 15:40   ` David Sterba
2013-08-01 17:59     ` Zach Brown
     [not found] ` <20130731225640.GO32145@lenny. home.zabbo.net>
2013-08-01  3:11   ` Duncan
2013-08-02 20:58 Mike Audia
2013-08-03  8:33 ` Duncan

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=51FD3FDC.803@skagestad.org \
    --to=lists@skagestad.org \
    --cc=hurikhan77+btrfs@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).