From: Sandon Van Ness <sandon@inktank.com>
To: Sage Weil <sage@redhat.com>
Cc: Loic Dachary <loic@dachary.org>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: ARM benchmarks for the erasure code plugin
Date: Fri, 27 Jun 2014 10:23:11 -0700 [thread overview]
Message-ID: <53ADA87F.8080808@inktank.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1406271016080.12946@cobra.newdream.net>
Yeah, they should be up and available as we are not testing them
anymore. They do have issues where they randomly went down before and if
any of them are down feel free to to hit me up and I can get them fixed up.
says37->saya44 are the newer machines that have the faster CPU's and
more ram and stuff (newer arch).
On 06/27/2014 10:16 AM, Sage Weil wrote:
> The machine types are tala and saya; you should be able to grab one with
> teuthology-lock. Hopefully they are up...
>
> sage
>
> On Fri, 27 Jun 2014, Loic Dachary wrote:
>
>> Hi Sandon,
>>
>> Would it be possible to get access to an ARM based machine to run erasure code plugins benchmarks ? The idea is to get a baseline similar to what https://github.com/ceph/ceph/pull/1875 shows and figure out where we stand. At this point any ARM processor will do. Eventually we will want to give NEON[1] enabled processors a try but right now we have nothing take advantage of that ;-)
>>
>> Cheers
>>
>> [1] http://en.wikipedia.org/wiki/NEON_%28instruction_set%29#NEON
>>
>> --
>> Lo?c Dachary, Artisan Logiciel Libre
>>
>>
next prev parent reply other threads:[~2014-06-27 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 17:12 ARM benchmarks for the erasure code plugin Loic Dachary
2014-06-27 17:16 ` Sage Weil
2014-06-27 17:23 ` Sandon Van Ness [this message]
2014-06-27 17:34 ` Loic Dachary
2014-06-27 20:34 ` Loic Dachary
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=53ADA87F.8080808@inktank.com \
--to=sandon@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.org \
--cc=sage@redhat.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.