public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@google.com>
To: Daniel Phillips <phillips@google.com>
Cc: Mark Fasheh <mark.fasheh@oracle.com>,
	Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>,
	ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [Ocfs2-devel] Ocfs2 performance
Date: Fri, 10 Mar 2006 13:13:03 -0800	[thread overview]
Message-ID: <4411EBDF.30104@google.com> (raw)
In-Reply-To: <44116057.5060705@google.com>

Going back to that mysterious idle time fluctuation problem, I just noticed
something interesting here:

> With hashvec, (64K buckets)
> 
>       real user sys
>     29.62 23.87 3.02
>     28.80 24.16 3.07
>     50.95 24.11 3.04
>     28.17 23.95 3.20
>     61.21 23.89 3.16
>     28.61 23.88 3.30
> 
> With vmalloc (64K buckets)
> 
>       real user sys
>     29.67 23.98 2.88
>     28.35 23.96 3.13
>     52.29 24.16 2.89
>     28.39 24.07 2.97
>     65.13 24.08 3.01
>     28.08 24.02 3.16

Look, the real time artifacts show up in the same places in the two
different runs.  There was a reboot before each run.  There is a sync
before  and after each trial.  Each trial was initiated by hand, so this
isn't about something else going on in the machine at the same time.

Got to be a clue in there somewhere.

Regards,

Daniel

  parent reply	other threads:[~2006-03-10 21:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-03 22:27 Ocfs2 performance bugs of doom Daniel Phillips
2006-03-04  0:53 ` Mark Fasheh
2006-03-04  3:42   ` Daniel Phillips
2006-03-04  7:36 ` Andrew Morton
2006-03-05 19:22   ` Mark Fasheh
2006-03-06  1:28   ` Daniel Phillips
2006-03-06  2:58     ` [Ocfs2-devel] " Mark Fasheh
2006-03-06  4:59       ` Daniel Phillips
2006-03-06 19:51         ` Mark Fasheh
2006-03-07  3:34           ` Andi Kleen
2006-03-07  4:58             ` Mark Fasheh
2006-03-07  6:56               ` [Ocfs2-devel] " Daniel Phillips
2006-03-09  6:26               ` Daniel Phillips
2006-03-09  7:26                 ` Nick Piggin
2006-03-09  7:43                 ` Nick Piggin
2006-03-09  4:19                   ` Andi Kleen
2006-03-09 12:30                     ` Nick Piggin
2006-03-10  5:14                       ` Nick Piggin
2006-03-10  0:21                 ` [Ocfs2-devel] Ocfs2 performance Mark Fasheh
2006-03-10  1:14                   ` Bernd Eckenfels
2006-03-10  7:10                     ` Joel Becker
2006-03-11  1:09                     ` Mark Fasheh
2006-03-11  1:57                       ` Bernd Eckenfels
2006-03-10 11:17                   ` Daniel Phillips
2006-03-10 18:23                     ` Zach Brown
2006-03-10 21:13                       ` Daniel Phillips
2006-03-10 21:13                     ` Daniel Phillips [this message]
2006-03-10  2:33                 ` [Ocfs2-devel] Ocfs2 performance bugs of doom J. Bruce Fields
2006-03-10 10:27                   ` Daniel Phillips

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=4411EBDF.30104@google.com \
    --to=phillips@google.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.fasheh@oracle.com \
    --cc=ocfs2-devel@oss.oracle.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