From: Mark Nelson <mnelson@redhat.com>
To: Robert LeBlanc <robert@leblancnet.us>,
Somnath Roy <Somnath.Roy@sandisk.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Ceph Write Path Improvement
Date: Thu, 03 Sep 2015 11:42:10 -0500 [thread overview]
Message-ID: <55E87862.5060809@redhat.com> (raw)
In-Reply-To: <CAANLjFpmO+rGnEFM5+u6piVoa4YqvoVCcTWjYOQJ2cXEEk7T-g@mail.gmail.com>
On 09/03/2015 11:23 AM, Robert LeBlanc wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Somnath,
>
> I'm having a hard time with your slide deck. Am I understanding
> correctly that the default Hammer install was performed on SSDs with
> co-located journals, but the optimized code was performed on the same
> SSDs but the journal was in NVRAM? If so I'm having a hard time
> understanding how these tests can be comparable. I really like the
> performance gains you are seeing, but I'm trying to understand how
> much the optimized code alone helps performance.
Hi Robert,
We talked about this a bit at the weekly performance meeting. I think
Somnath just hasn't gotten a chance to do those tests yet and is
planning on doing them in the coming weeks. I believe he started out
with hammer on the SSDs and then tried to figure out how to tweak things
to make the NVRAM configuration perform better. Now he has to go back
and retest the original configuration but with the new code.
Mark
next prev parent reply other threads:[~2015-09-03 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 23:06 Ceph Write Path Improvement Somnath Roy
2015-09-03 16:23 ` Robert LeBlanc
2015-09-03 16:42 ` Mark Nelson [this message]
2015-09-03 17:38 ` Robert LeBlanc
2015-09-03 17:42 ` Somnath Roy
2015-09-03 20:01 ` Blinick, Stephen L
2015-09-03 20:06 ` Somnath Roy
2015-09-10 0:33 ` Somnath Roy
2015-09-10 17:20 ` Robert LeBlanc
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=55E87862.5060809@redhat.com \
--to=mnelson@redhat.com \
--cc=Somnath.Roy@sandisk.com \
--cc=ceph-devel@vger.kernel.org \
--cc=robert@leblancnet.us \
/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.