From: Junxiao Bi <junxiao.bi@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] OCFS2 benchmark questions
Date: Wed, 25 May 2016 10:34:59 +0800 [thread overview]
Message-ID: <57450F53.70602@oracle.com> (raw)
In-Reply-To: <573F3B8C020000F900037F05@prv-mh.provo.novell.com>
On 05/20/2016 04:30 PM, Gang He wrote:
> Hello Joseph, Junxiao and All,
>
> I got some benchmark related questions, but due to hardware limitation in our local lab, we have not enough information to answer the questions.
> Could you help to look at the questions, if you ever did the related testings in your sites.
> 1) How many nodes can OCFS2 cluster scale out to? theoretically, the answer is 32. but who ever did the testing with the maximum number of nodes? second, too many nodes will impact the performance, or not?
The limit is 255, but we didn't advise using more than 32 nodes. More
nodes impact performance for sure.
Thanks,
Junxiao.
>
> 2) Who can help to share OCFS2 benchmark information/data in the physical environment? e.g. node hardware information, back-end storage information, IO read/write data, IOPS/IO throughput. etc.
>
>
> Thanks
> Gang
>
>
next prev parent reply other threads:[~2016-05-25 2:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 8:30 [Ocfs2-devel] OCFS2 benchmark questions Gang He
2016-05-25 2:34 ` Junxiao Bi [this message]
2016-05-25 3:44 ` Joseph Qi
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=57450F53.70602@oracle.com \
--to=junxiao.bi@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).