All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Trofimovich <slyich@gmail.com>
To: "Szőts Ákos" <szotsaki@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: systemd "journalctl" is 1.89sec on ext4, 1.49 min on btrfs
Date: Mon, 27 May 2013 20:47:23 +0300	[thread overview]
Message-ID: <20130527204723.573c4e3f@sf> (raw)
In-Reply-To: <16735484.PAleCPYpY8@noname>

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

On Mon, 27 May 2013 18:21:21 +0200
Szőts Ákos <szotsaki@gmail.com> wrote:

> Dear list,
> 
> I have two openSUSE 12.3 systems with kernel 3.9. On one of them there's an 
> ext4 partition, while on the other there's a btrfs.
> 
> I issued a "time journalctl -b --no-pager" command on both systems. This shows 
> the logs from the current boot without passing them to "less".
> 
> On ext4 (3.9.3):
> real    0m1.898s
> user    0m0.291s
> sys     0m0.105s
> 
> On btrfs (3.9.2):
> real    1m49.698s
> user    0m0.102s
> sys     0m0.470s
> 
> 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.
> 
> Is it a known issue or can I help somehow debugging this further?

Let's look at your
    /usr/sbin/filefrag /var/log/journal/*/*
on both systems

-- 

  Sergei

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

  parent reply	other threads:[~2013-05-27 17:48 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
2013-05-27 16:42 ` George Mitchell
2013-05-27 17:47 ` Sergei Trofimovich [this message]
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=20130527204723.573c4e3f@sf \
    --to=slyich@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=szotsaki@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.