linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: Hugo Mills <hugo@carfax.org.uk>
Cc: "Swâmi Petaramesh" <swami@petaramesh.org>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Rename BTRfs to MuchSlowerFS ?
Date: Mon, 5 Sep 2011 20:20:00 +0600	[thread overview]
Message-ID: <20110905202000.4c539297@natsu> (raw)
In-Reply-To: <20110905140023.GP9907@carfax.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1569 bytes --]

On Mon, 5 Sep 2011 15:00:23 +0100
Hugo Mills <hugo@carfax.org.uk> wrote:
> > 
> > BTRFS machine took 20 HOURS so far, still counting (ETA 15 minutes left).
> > 
> > Wow. Impressive.
> 
>    That's because dpkg is known for using (f)sync very heavily.  btrfs
> honours the sync request in all cases

I don't think it's *just* that.

I had the same problem, recently upgrading Debian from Stable to Testing, it was taking more than 24 hours. I stopped the upgrade, then resumed it this time via eatmydata, and it proceeded perhaps two orders of magnitude faster than before, finishing the remaining packages in 5 minutes or so.

Problem is, even when I stopped the upgrade and waited a considerable time, each 'sync' was still taking 5-7 seconds. No other disk activity in the system, no snapshot creation/deletion/cleanup going on either, just multiple consecutive syncs:

rm@rm:~$ time sync

real	0m4.772s
user	0m0.000s
sys	0m0.480s
rm@rm:~$ time sync

real	0m6.831s
user	0m0.000s
sys	0m0.472s
rm@rm:~$ time sync

real	0m8.069s
user	0m0.000s
sys	0m0.468s
rm@rm:~$ time sync

real	0m6.675s
user	0m0.000s
sys	0m0.464s
rm@rm:~$ time sync

real	0m4.293s
user	0m0.000s
sys	0m0.464s
rm@rm:~$ time sync

real	0m4.230s
user	0m0.000s
sys	0m0.472s
rm@rm:~$ time sync

real	0m6.924s
user	0m0.000s
sys	0m0.464s

To be fair, this was on the 2.6.39.2 kernel, and the performance seems to be somewhat better on 3.0 (though I didn't do tests like this one or any significant dpkg operations on it yet).

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-09-05 14:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-05 13:51 Rename BTRfs to MuchSlowerFS ? Swâmi Petaramesh
2011-09-05 14:00 ` Hugo Mills
2011-09-05 14:20   ` Roman Mamedov [this message]
2011-09-05 17:10     ` Elric Milon
2011-09-05 14:17 ` David McBride
2011-09-05 19:25 ` Sergei Trofimovich
2011-09-06 15:30   ` Swâmi Petaramesh
2011-09-06 17:11     ` Fajar A. Nugraha
2011-09-07 14:15       ` Swâmi Petaramesh
2011-09-15 19:37         ` Felix Blanke
2011-09-15 22:16           ` Fajar A. Nugraha
2011-09-16  6:21             ` Maciej Marcin Piechotka
2011-09-16  6:42               ` Fajar A. Nugraha
2011-09-16  8:39                 ` Maciej Marcin Piechotka
  -- strict thread matches above, loose matches on Subject: below --
2011-09-05 16:23 Tomasz Chmielewski
2011-09-05 16:25 ` Christoph Hellwig
2011-09-05 16:29   ` Hugo Mills
2011-09-08  7:04     ` youagree

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=20110905202000.4c539297@natsu \
    --to=rm@romanrm.ru \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=swami@petaramesh.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).