All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Starek <quiterigorouslyfilteredusenetaccount@gmx.de>
To: reiserfs-list@namesys.com
Subject: Re: ReiserFS slow, need help diagnosing
Date: Mon, 05 Jun 2006 16:29:48 +0200	[thread overview]
Message-ID: <e61f4n$p6b$1@sea.gmane.org> (raw)
In-Reply-To: 1149516737.6402.120.camel@tribesman.namesys.com

Vladimir V. Saveliev schrieb:
> On Mon, 2006-06-05 at 15:11 +0200, Juergen Starek wrote:
>
>> I have noticed that if I put my ~ on a ReiserFS partition, Pan (GNOME's
>> newsreader) starts very slowly, [...]
> 
> Probably Pan is stat(2)-ing whole cache. Can you please try to find out
> what Pan is doing on start? Strace(1) may help.

You're right, I straced Pan's start process and after initialization, it
seems to call stat64 on every message in its cache. This is a snippet of
the trace, produced on an ext3 filesystem (line length exceeds 80 chars): 

==========
stat64("/home/jstarek/.pan/gmane", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/home/jstarek/.pan/Standard", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0

stat64("/home/jstarek/.pan/messages/cache", {st_mode=S_IFDIR|0755, st_size=1032192, ...}) = 0
open("/home/jstarek/.pan/messages/cache", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 6
fstat64(6, {st_mode=S_IFDIR|0755, st_size=1032192, ...}) = 0
fcntl64(6, F_SETFD, FD_CLOEXEC)         = 0
getdents64(6, /* 62 entries */, 4096)   = 4096
stat64("/home/jstarek/.pan/messages/cache/42b4e3b2$0$1128$9b4e6d93@newsread4.arcor-online.net.msg", {st_mode=S_IFREG|0644, st_size=1426, ...}) = 0
time(NULL)                              = 1149517138
==========

The last two calls of this trace snippet are then repeated for all files
in the cache.

> If Pan is doing millions of stats for files from cache - that explains
> why it starts slowly when cache is stored on reiserfs.

Could you please explain this? An URL with the explanation is fine, too --
I just don't have experience with file systems...

Thanks,

  Jürgen


  reply	other threads:[~2006-06-05 14:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-05 13:11 ReiserFS slow, need help diagnosing Juergen Starek
2006-06-05 14:12 ` Vladimir V. Saveliev
2006-06-05 14:29   ` Juergen Starek [this message]
2006-06-05 15:16     ` Vladimir V. Saveliev
2006-06-05 15:34       ` Grzegorz Kulewski
2006-06-05 15:54         ` Vladimir V. Saveliev
2006-06-05 16:08           ` Grzegorz Kulewski
2006-06-05 16:22             ` Hans Reiser
2006-06-05 17:09               ` Jonathan Briggs
2006-06-05 22:05               ` Juergen Starek
2006-06-05 16:20       ` Hans Reiser

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='e61f4n$p6b$1@sea.gmane.org' \
    --to=quiterigorouslyfilteredusenetaccount@gmx.de \
    --cc=reiserfs-list@namesys.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.