linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.70-mm1
Date: Thu, 29 May 2003 11:52:37 -0700	[thread overview]
Message-ID: <20030529115237.33c9c09a.akpm@digeo.com> (raw)
In-Reply-To: <18080000.1054233607@[10.10.2.4]>

"Martin J. Bligh" <mbligh@aracnet.com> wrote:
>
> > SDET 128  (see disclaimer)
> >                            Throughput    Std. Dev
> >                2.5.66-mm2       100.0%         0.6%
> >           2.5.66-mm2-ext3         3.9%         0.4%
> > 
> > SDET 128  (see disclaimer)
> >                            Throughput    Std. Dev
> >           2.5.70-mm1-ext2       100.0%         0.1%
> >           2.5.70-mm1-ext3        22.7%         2.0%
> 
> Andrew pointed out I should turn off extended attributes, I reran
> like this ... not much change (with error margins)
> 
>  SDET 32  (see disclaimer)
>                            Throughput    Std. Dev
>           2.5.70-mm1-ext2       100.0%         0.2%
>           2.5.70-mm1-ext3        30.9%         7.8%
>           2.5.70-mm1-noxa        34.6%         6.5%

OK, a 10x improvement isn't too bad.  I'm hoping the gap between ext2 and
ext3 is mainly idle time and not spinning-on-locks time.


> 
>    2024927   267.3% total
>    1677960   472.8% default_idle
>     116350     0.0% .text.lock.transaction
>      42783     0.0% do_get_write_access
>      40293     0.0% journal_dirty_metadata
>      34251  6414.0% __down
>      27867  9166.8% .text.lock.attr

Bah.  In inode_setattr(), move the mark_inode_dirty() outside
lock_kernel().

>      20016  2619.9% __wake_up
>      19632   927.4% schedule
>      12204     0.0% .text.lock.sched
>      12128     0.0% start_this_handle
>      10011     0.0% journal_add_journal_head

hm, lots of context switches still.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2003-05-29 18:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-27  7:42 2.5.70-mm1 Andrew Morton
2003-05-27 10:38 ` 2.5.70-mm1 Marc-Christian Petersen
2003-05-27 20:33   ` 2.5.70-mm1 Ed Tomlinson
2003-05-27 20:49     ` 2.5.70-mm1 Andrew Morton
2003-05-27 23:05       ` 2.5.70-mm1 Ed Tomlinson
2003-05-28 17:10 ` 2.5.70-mm1 Mingming Cao
2003-05-28 19:44   ` 2.5.70-mm1 Andrew Morton
2003-05-29  6:23 ` 2.5.70-mm1 Martin J. Bligh
2003-05-29 18:40   ` 2.5.70-mm1 Martin J. Bligh
2003-05-29 18:52     ` Andrew Morton [this message]
2003-05-29 20:30       ` 2.5.70-mm1 Martin J. Bligh
2003-05-29 21:14         ` 2.5.70-mm1 Andrew Morton
2003-05-30 15:51           ` 2.5.70-mm1 Martin J. Bligh
2003-05-30 16:43             ` 2.5.70-mm1 Andrew Morton
2003-05-30 23:51               ` 2.5.70-mm1 Martin J. Bligh
2003-06-03  6:34                 ` ext3 semaphore tracing Martin J. Bligh
2003-05-28 13:26 2.5.70-mm1 Downing, Thomas

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=20030529115237.33c9c09a.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@aracnet.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