From: Mark Nelson <mark.nelson@inktank.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Patrick McGarry <patrick@inktank.com>,
Ceph Devel <ceph-devel@vger.kernel.org>
Subject: Re: Bobtail vs Argonaut Performance Preview
Date: Sat, 22 Dec 2012 07:36:41 -0600 [thread overview]
Message-ID: <50D5B769.4090104@inktank.com> (raw)
In-Reply-To: <20121222083200.GA1977@infradead.org>
On 12/22/2012 02:32 AM, Christoph Hellwig wrote:
> On Thu, Dec 20, 2012 at 11:08:19AM -0500, Patrick McGarry wrote:
>> Hey All,
>>
>> Inktank's Mark Nelson just posted a great performance preview of
>> Bobtail with comparison to Argonaut. Feel free to check it out:
>>
>> http://ow.ly/gg87B
>
> What's the problem with using a proper link instead of these idiotic
> shortening services?
I think it's just the twitter world leaking out into other mediums.
Some times it's slightly bewildering to me that in this day and age so
much conversation seems to happen on a medium that only allows 140
characters at a time. That's apparently the world we live in though. :)
Btw Christoph, thank you for taking the time to read my article. If
I've done anything dumb or suboptimal regarding xfs, please do let me
know. Soon I will be doing parametric sweeps over ceph parameter spaces
to see how performance varies on different hardware configurations. I
want to make sure the tests are setup as optimally as possible.
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Mark
next prev parent reply other threads:[~2012-12-22 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 16:08 Bobtail vs Argonaut Performance Preview Patrick McGarry
2012-12-22 8:32 ` Christoph Hellwig
2012-12-22 13:36 ` Mark Nelson [this message]
2012-12-22 16:28 ` Patrick McGarry
2012-12-22 18:45 ` Christoph Hellwig
2012-12-22 19:44 ` Mark Nelson
2012-12-22 19:46 ` Christoph Hellwig
2012-12-27 22:17 ` Stefan Priebe
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=50D5B769.4090104@inktank.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=hch@infradead.org \
--cc=patrick@inktank.com \
/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.