All of lore.kernel.org
 help / color / mirror / Atom feed
* [Ocfs2-devel] OCFS2 benchmark questions
@ 2016-05-20  8:30 Gang He
  2016-05-25  2:34 ` Junxiao Bi
  0 siblings, 1 reply; 3+ messages in thread
From: Gang He @ 2016-05-20  8:30 UTC (permalink / raw)
  To: ocfs2-devel

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?

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  

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Ocfs2-devel] OCFS2 benchmark questions
  2016-05-20  8:30 [Ocfs2-devel] OCFS2 benchmark questions Gang He
@ 2016-05-25  2:34 ` Junxiao Bi
  2016-05-25  3:44   ` Joseph Qi
  0 siblings, 1 reply; 3+ messages in thread
From: Junxiao Bi @ 2016-05-25  2:34 UTC (permalink / raw)
  To: ocfs2-devel

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  
> 
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Ocfs2-devel] OCFS2 benchmark questions
  2016-05-25  2:34 ` Junxiao Bi
@ 2016-05-25  3:44   ` Joseph Qi
  0 siblings, 0 replies; 3+ messages in thread
From: Joseph Qi @ 2016-05-25  3:44 UTC (permalink / raw)
  To: ocfs2-devel

On 2016/5/25 10:34, Junxiao Bi wrote:
> 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.

IMO, benchmark depends on user scenarios.
For the scalability, I think the number of messages is one of the main
impact factors. And more nodes will increase fault probability.

Thanks,
Joseph

>>
>> 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  
>>
>>
> 
> 
> .
> 

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2016-05-25  3:44 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-05-20  8:30 [Ocfs2-devel] OCFS2 benchmark questions Gang He
2016-05-25  2:34 ` Junxiao Bi
2016-05-25  3:44   ` Joseph Qi

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.