All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fan Yong <yong.fan@whamcloud.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Large readdir RPCs project
Date: Thu, 30 Sep 2010 09:56:54 +0800	[thread overview]
Message-ID: <4CA3EE66.2040206@whamcloud.com> (raw)
In-Reply-To: <AANLkTi=q2XwYnhWPRUJha-o8dxCV5DZ6_so_P5RbHzN4@mail.gmail.com>

  On 9/30/10 3:01 AM, Jeremy Filizetti wrote:
>
>
>     On the other hand, Large readdir RPCs is basic of another metadata
>     read performance improvement features - "readdir+", which is quite
>     useful for "ls -l" operation (for large directory), and reduce
>     lookup/getattr RPC as much as possible. In such feature, MDS will
>     pack more dir-item's attribute (not only name/ino as does
>     currently by readdir, but also mode/owner, and etc) information
>     back to client-side in "readdir+" RPC. That means the dir-item
>     count in one "readdir+" page is less than in the traditional
>     readdir page, then more pages to be sent back to client. If
>     without "Large readdir RPCs", the advantage of "readdir+" will be
>     discounted.
>
> I'd be interested in working this as well but probably as a separate 
> effort since SOM isn't in 1.8 and that's my main focus.  In our 
> testing, SOM had significant benefits over the WAN and I'd expect even 
> better from readdir+.  I have tried Oleg's patch for 
> asynchronous ll_glimpse_size but oddly I've seen someone erradic 
> performance where at times it was worse then statahead and synchronous 
> ll_glimpse_size.
> Jeremy
Yes, SOM is another important feature for metadata reading performance 
improvement by bypassing the glimpse RPC between client and OSS. 
Engineers from Lustre Group worked for that for some time, hope can be 
released soon.

As for the asynchronous ll_glimpse_size maybe cause bad performance 
occasionally, one possible reason is that: glimpse RPC maybe not obtain 
extent lock(s) if some others in using such lock(s), so the file size 
information obtained by asynchronous glimpse is invalid when it is 
really used later, means the caller ("stat") has to send synchronous 
glimpse again. Anyway, I did not study such patch, so it is just a guess.


Cheers,
Nasf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20100930/1f1bb1a1/attachment.htm>

  reply	other threads:[~2010-09-30  1:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 13:14 [Lustre-devel] Large readdir RPCs project Jeremy Filizetti
2010-09-29  7:44 ` Fan Yong
2010-09-29 19:01   ` Jeremy Filizetti
2010-09-30  1:56     ` Fan Yong [this message]
2010-10-13 16:04       ` Jeremy Filizetti
2010-10-13 16:32         ` Fan Yong

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=4CA3EE66.2040206@whamcloud.com \
    --to=yong.fan@whamcloud.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.