From: Loic Dachary <loic@dachary.org>
To: Derek Su <dereksu@qnap.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: About the Ceph erasure pool with ISA plugin on Intel xeon CPU
Date: Thu, 06 Aug 2015 14:31:02 +0200 [thread overview]
Message-ID: <55C35386.6070602@dachary.org> (raw)
In-Reply-To: <CAKEOLWVxuURSgYP3FLRhHs=THuYK0Qy084hNxZAqERyAYy2J4w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
Hi,
Could you please publish the benchmark results somewhere ? I should be able to figure out why you don't see a difference.
Cheers
On 06/08/2015 13:25, Derek Su wrote:
> Dear Mr. Dachary and all,
>
> Recently, I found your blog show the performance tests of erasure
> pools (http://dachary.org/?p=3042 , http://dachary.org/?p=3665).
> The results indicates the write throughput can be enhanced
> significantly using Intel xeon CPU.
>
> I tried to create an erasure pool with isa plugin, reed_sol_van
> technique, and k/m=4/2 on the Intel(R) Xeon(R) CPU E3-1245 v3 @
> 3.40GHz machines.
>
> However, the results of the rados benchmark showed that there was no
> any difference between the jerasure and isa plugins. It seems very
> strange.
>
> Do I need to do other configurations in addition to only setting the
> erasure profile?
> In addition, how can I know the erasure pool is accelerated by ISA
> plugin exactly? Is there any command I can use?
>
> Thanks, :)
>
> Derek Su.
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-08-06 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 11:25 About the Ceph erasure pool with ISA plugin on Intel xeon CPU Derek Su
2015-08-06 12:31 ` Loic Dachary [this message]
2015-08-07 1:26 ` Derek Su
2015-08-07 9:25 ` Loic Dachary
2015-08-07 9:45 ` Derek Su
2015-08-07 10:43 ` 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=55C35386.6070602@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dereksu@qnap.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.