All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: Solofo.Ramangalahy@bull.net, "Theodore Ts'o" <tytso@mit.edu>,
	linux-ext4@vger.kernel.org
Subject: Re: jbd/jbd2 performance improvements
Date: Thu, 16 Oct 2008 07:39:04 -0500	[thread overview]
Message-ID: <48F735E8.7060803@redhat.com> (raw)
In-Reply-To: <48F72E5F.2050409@redhat.com>

Ric Wheeler wrote:
> Solofo.Ramangalahy@bull.net wrote:
>> Hi Ric,
>>
>>   
>>>>>>> On Wed, 15 Oct 2008 13:29:55 -0400, Ric Wheeler <rwheeler@redhat.com> said:
>>>>>>>             
>>     Ric> We are going to try and poke at this - do you suspect a single or 
>>     Ric> multi-threaded test would work best?
>>
>> I've performed some tests:
>> http://www.bullopensource.org/ext4/20081013-2.6.27-rc9-ext4-1-akpm-fix-run6/
>> http://www.bullopensource.org/ext4/20081013-2.6.27-rc9-ext4-1-akpm-fix-run6/results_sorted.txt.html
>>
>> I now realize that the results may not be valid since I used kvm, but
>> they do show variation wrt. the number of threads.
>>
>> So you may want to test both single and multi-threaded.
>>
>>   
> A very thorough test, but the results don't seem to point to a 
> consistent winner.
> 
> I agree that running without KVM in the picture might be very 
> interesting. Eric has some similar tests underway, I think that his 
> results were also inconclusive so far...

Yep, I've yet to find an fs_mark invocation, at least, which shows a
clear winner.  I also ran w/ akpm's suggested io_schedule watcher patch
and never see us waiting on this lock (I did set it to 1s though, which
is probably too long for my storage).

-Eric

  reply	other threads:[~2008-10-16 12:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07 13:14 jbd/jbd2 performance improvements Theodore Ts'o
2008-10-15 17:29 ` Ric Wheeler
2008-10-16  6:04   ` Solofo.Ramangalahy
2008-10-16 12:06     ` Ric Wheeler
2008-10-16 12:39       ` Eric Sandeen [this message]
2008-10-23 10:42         ` Solofo.Ramangalahy
2008-10-23 12:00           ` Ric Wheeler
2008-10-23 12:22             ` Solofo.Ramangalahy

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=48F735E8.7060803@redhat.com \
    --to=sandeen@redhat.com \
    --cc=Solofo.Ramangalahy@bull.net \
    --cc=linux-ext4@vger.kernel.org \
    --cc=rwheeler@redhat.com \
    --cc=tytso@mit.edu \
    /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.