All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Fertman <Vitaly.Fertman@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] LustreFS performance
Date: Tue, 10 Mar 2009 19:40:53 +0300	[thread overview]
Message-ID: <861E8C51-4422-4C51-9062-DC3916DB96D6@Sun.COM> (raw)
In-Reply-To: <49B65524.6080707@sun.com>

On Mar 10, 2009, at 2:55 PM, Mallik Ragampudi wrote:

> Vitaly,
>
> This is very comprehensive. Few comments:
>
> 1) I think it would be good to start with LLT2 (lustre-iokit: ior- 
> survey) and get an out-of-the-box performance
> picture/comparison (1.6 and 2.0) from the whole cluster before  
> testing the individual layers.

LLT2 is about underlying local fs on servers, not Lustre.
the overall ior-survey is OSTT3 (it was wrongly mentioned as ost-survey
in the document header, sorry, it must be ior-survey as written
in the detailed section)

> 2) Can this plan be extended to include CMD performance testing as  
> well ? I would expect that most
> of your test cases apply for the CMD as well ?

sure, I will extend it.

> 3) I assume the "CPU" parameter in your methodology refers to # of  
> CPUs in MDS, right ?

to the server which is being tested at the moment, i.e. OST for OST*  
tests,
MDS fro MDS* tests. In the mixed section it refers to MDS indeed.

> 4) I am not sure if we can test 32 cores without hitting other  
> bottlenecks beyond 8 coress on the servers.

if we hit some bottleneck, we will get a problem to solve, what is  
good ;)
however, to see the bottleneck from these results, it is better to run  
MT
tests with different amount of CPUs (the same as for all the CPU  
tests, 1,2,8,32).

> This will cut down some combinations in the matrix.
>
> Thanks,
> Mallik
>

--
Vitaly

  reply	other threads:[~2009-03-10 16:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3376C558-E29A-4BB5-8C4C-3E8F4537A195@sun.com>
     [not found] ` <02FEAA2B-8D98-4C2D-9CE8-FF6E1EB135A2@sun.com>
2009-03-02 17:04   ` [Lustre-devel] LustreFS performance Vitaly Fertman
2009-03-02 20:45     ` Andreas Dilger
2009-03-04 17:19       ` Oleg Drokin
2009-03-04 17:28         ` Jeff Darcy
2009-03-05 21:27           ` Andreas Dilger
2009-03-09  2:50             ` Oleg Drokin
2009-03-09  8:29               ` Andreas Dilger
2009-03-10 14:39       ` Nicholas Henke
2009-03-10 15:07         ` Mark Seger
2009-03-10 11:55     ` Mallik Ragampudi
2009-03-10 16:40       ` Vitaly Fertman [this message]
2009-03-19 19:34   ` [Lustre-devel] LustreFS performance (update) Vitaly Fertman
2009-03-19 20:16     ` Andrew C. Uselton
2009-03-20 13:15       ` Vitaly Fertman
2009-03-20  5:47     ` parinay kondekar
2009-03-24  0:34       ` Eric Barton

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=861E8C51-4422-4C51-9062-DC3916DB96D6@Sun.COM \
    --to=vitaly.fertman@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.