All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sage Weil <sage@newdream.net>
To: Fyodor Ustinov <ufm@ufm.su>
Cc: ceph-devel@vger.kernel.org
Subject: Re: read performance not perfect
Date: Fri, 5 Aug 2011 13:17:02 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.1108051315420.12301@cobra.newdream.net> (raw)
In-Reply-To: <4E3C44DC.9090906@ufm.su>

On Fri, 5 Aug 2011, Fyodor Ustinov wrote:
> On 08/05/2011 07:07 PM, Sage Weil wrote:
> > 
> > This is the problem.  The readahead patches in the master branch of
> > git://ceph.newdream.net/git/ceph-client.git.  They're not upstream yet.
> > Sorry that wasn't clear!
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=e9852227431a0ed6ceda064f33e4218757acab6c
> - it's not this patch?

Nope, it's ebd62c49c0a71a9af6b92b4f0cedfd2b1d46c16e, in ceph-client.git.  
Then d0a287e18a81a0314a9aa82b6f54eb7f5ecabd60 bumps up the default rasize
window.

FWIW I saw a big jump in read spead on my cluster (now fully saturates the 
client interface).

sage

  parent reply	other threads:[~2011-08-05 20:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18  4:51 read performance not perfect huang jun
2011-07-18 17:14 ` Sage Weil
2011-07-20  0:21   ` huang jun
     [not found]   ` <CABAwU-YKmEC=umFLzDb-ykPbzQ9s3sKoUmQbkumExrXEwyveNA@mail.gmail.com>
2011-08-04 15:51     ` Sage Weil
2011-08-04 19:36       ` Fyodor Ustinov
2011-08-04 19:53         ` Sage Weil
2011-08-04 23:38           ` Fyodor Ustinov
2011-08-05  1:26             ` Sage Weil
2011-08-05  6:34               ` Fyodor Ustinov
2011-08-05 16:07                 ` Sage Weil
2011-08-05 19:30                   ` Fyodor Ustinov
2011-08-05 19:35                     ` Gregory Farnum
2011-08-05 20:17                     ` Sage Weil [this message]
2011-08-05 21:12                       ` Fyodor Ustinov
2011-08-08 17:52                         ` Fyodor Ustinov
2011-08-08 19:14                           ` Sage Weil
2011-08-06 11:03                   ` Fyodor Ustinov
2011-08-06 19:08                     ` Sage Weil
2011-08-09  3:56       ` huang jun

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=Pine.LNX.4.64.1108051315420.12301@cobra.newdream.net \
    --to=sage@newdream.net \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ufm@ufm.su \
    /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.