All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Zhuravlev <Alex.Zhuravlev@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Some investigations on  MDS creation rate
Date: Mon, 16 Feb 2009 18:26:31 +0300	[thread overview]
Message-ID: <499985A7.7000600@sun.com> (raw)
In-Reply-To: <FE7ACA5E-C11C-41B7-BF1D-05F9A73C72DF@sun.com>

Oleg Drokin wrote:
>    I also performed tests on HEAD and it performs significantly worse  
> (5.8k at most). Even with all the same fixes ported from b1_6.
>    The CPU remains the same and I used lock meter to verify that there  
> is no significant lock contention.
>    Looking into the oprofile results, it looks like all code just  
> became slower (judging by more hits in various areas for the same  
> workload).
>    Also some parts of the code are now more heavily loaded (ptlrpc 
> +ldlm in HEAD draws more cpu time, llite portion of the code is 50%  
> more time

notice HEAD takes two ldlm locks for each create, 1.6 takes one.

>    I have no idea why the variability and I do not see anything very  
> obvious that would explain sudden overall performance degradation of  
> HEAD code either yet.

it would  be interesting to gather L1/L2 cache hit/miss with oprofile for
1.6 and HEAD.

thanks, Alex

  reply	other threads:[~2009-02-16 15:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-14  8:47 [Lustre-devel] Some investigations on MDS creation rate Oleg Drokin
     [not found] ` <49982E71.80902@cray.com>
2009-02-16  0:10   ` Oleg Drokin
2009-02-16 11:11 ` Oleg Drokin
2009-02-16 15:26   ` Alex Zhuravlev [this message]
2009-02-16 21:05     ` Oleg Drokin
2009-02-17  6:17       ` Alex Zhuravlev

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=499985A7.7000600@sun.com \
    --to=alex.zhuravlev@sun.com \
    --cc=lustre-devel@lists.lustre.org \
    /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.