From: Clemens Eisserer <linuxhippy@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: systemd "journalctl" is 1.89sec on ext4, 1.49 min on btrfs
Date: Mon, 27 May 2013 18:36:14 +0200 [thread overview]
Message-ID: <CAFvQSYRjPycUL0vuKeWEUUcXQC9cUGwLT1uSz3DPFGxLYze1gA@mail.gmail.com> (raw)
In-Reply-To: <CAFvQSYTtuH99nqMb6589xJgwsrSG6fD02XzU3ji=dSmJokMxTw@mail.gmail.com>
Hi,
>> Journalctl on btrfs was always this slow, some btrfsck were made on the file
>> system too, but I don't think it was corrupted. On just the first run it's
>> sluggish, after it's fast as the ext4 one.
Most likely the file is heavily fragmented due to COW.
Have you tried to manually defrag the filesystem and turn on autodefrag?
Regards, Clemens
next prev parent reply other threads:[~2013-05-27 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 16:21 systemd "journalctl" is 1.89sec on ext4, 1.49 min on btrfs Szőts Ákos
[not found] ` <CAFvQSYTtuH99nqMb6589xJgwsrSG6fD02XzU3ji=dSmJokMxTw@mail.gmail.com>
2013-05-27 16:36 ` Clemens Eisserer [this message]
2013-05-27 16:42 ` George Mitchell
2013-05-27 17:47 ` Sergei Trofimovich
2013-05-27 22:00 ` Szőts Ákos
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=CAFvQSYRjPycUL0vuKeWEUUcXQC9cUGwLT1uSz3DPFGxLYze1gA@mail.gmail.com \
--to=linuxhippy@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).