From: Stan Hoeppner <stan@hardwarefreak.com>
To: Hans-Peter Jansen <hpj@urpla.net>
Cc: Peter Landmann <sfrazt@googlemail.com>, linux-raid@vger.kernel.org
Subject: Re: Solving the raid write performance problems
Date: Tue, 02 Apr 2013 11:10:41 -0500 [thread overview]
Message-ID: <515B0301.7030002@hardwarefreak.com> (raw)
In-Reply-To: <2420596.ZXG94NVieB@xrated>
On 4/2/2013 8:29 AM, Hans-Peter Jansen wrote:
> Next, check, if you can address Stan Hoeppner's remarks from that thread.
>
> Compare test runs with variation in # of cores and numa affinity, nothing
> else. Be careful about the SSD state regarding wear leveling. Provide
> performance comparison charts.
NUMA affinity is only applicable for multi-socket systems, or single
socket systems using a dual die MCM CPU, such as the AMD Magny Cours and
Interlagos. Thus any work on NUMA optimization requires such a system,
or possibly a simulator.
--
Stan
next prev parent reply other threads:[~2013-04-02 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 11:36 Solving the raid write performance problems Peter Landmann
2013-04-02 13:29 ` Hans-Peter Jansen
2013-04-02 16:10 ` Stan Hoeppner [this message]
2013-04-02 14:14 ` keld
2013-04-02 16:33 ` Piergiorgio Sartor
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=515B0301.7030002@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=hpj@urpla.net \
--cc=linux-raid@vger.kernel.org \
--cc=sfrazt@googlemail.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.