From: fdegrassi <francesco.degrassi@emaze.net>
To: linux-xfs@oss.sgi.com
Subject: Re: Possible performance problem introduced between kernel 2.6.15 and 2.6.17 on xfs code
Date: Sun, 24 Dec 2006 01:36:29 +0100 [thread overview]
Message-ID: <458DCB8D.3040804@emaze.net> (raw)
In-Reply-To: <458D4EEB.3060501@sandeen.net>
The specific problem is related to gnome point-n-click only.
Anyway, I could be wrong, but i don't think it is a bug in gnome because:
1. it affects specifically local XFS filesystems only
2. the problem is not present on kernel 2.6.15 (I tested 2.6.17 and
2.6.15, both on ubuntu 6.10)
3. the problem does not manifest if i disable the call to
gnome_vfs_forget_cache, that, for what i understand, simply calls
fadvice POSIX_FADV_DONTNEED.
More info can be found on gnome bugzilla entry.
Francesco Degrassi
Eric Sandeen wrote:
> fdegrassi wrote:
>> Hi all,
>> i noticed that changing from kernel 2.6.15 to 2.6.17, gnomevfs-copy
>> operations suffered an heavy performance hit (20 times slower).
>> I checked quickly (i am not a kernel hacker) and i think it could be
>> related to libgnomevfs calling fadvice POSIX_FADV_DONTNEED (in
>> gnome_vfs_forget_cache, disabling this behaviour gets back normal
>> performance).
>> I am not able to dig deeper than this, anyway it could be a starting
>> point.
>> The relevant gnome bugzilla reference is the following:
>> http://bugzilla.gnome.org/show_bug.cgi?id=363400
>>
>> Francesco Degrassi
>>
>>
>
> Is a copy command from the shell affected, or just gnome point-n-click?
>
> -Eric
next prev parent reply other threads:[~2006-12-24 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-23 15:16 Possible performance problem introduced between kernel 2.6.15 and 2.6.17 on xfs code fdegrassi
2006-12-23 15:44 ` Eric Sandeen
2006-12-24 0:36 ` fdegrassi [this message]
2006-12-27 15:41 ` Eric Sandeen
2006-12-27 18:03 ` Francesco Degrassi
2006-12-27 18:05 ` Iustin Pop
2006-12-28 9:56 ` Francesco Degrassi
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=458DCB8D.3040804@emaze.net \
--to=francesco.degrassi@emaze.net \
--cc=linux-xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox