Performance of an aggregate is the total sum of spindles across the entire aggregate.
There is no 'raid group size' in the above sentence.
If you have TEN 2+1 raid groups, think about it this way..you have a 20 drive RAID0 stripe of IOPS available to you. Not ten separate buckets of two.
Forget parity as a limitation to system performance, you dont have a system large enough to worry about it.*
*: If you have a monstrous system, ya, you can remotely measure some overhead with 64b aggregates if you have 18 raid groups -vs- 7 raid groups with the difference being raid group size. The issue isnt the 64b aggregate structure, its just the # of raid zones to manage on writes. No surprise there...just drawing out an obscene example. :) But either way, you still have the same # of drives at work in the total stripe.
-----Original Message-----
From: Adam Levin [mailto:levins@westnet.com]
Sent: Monday, October 31, 2011 6:52 AM
To: Cotton, Randall
Cc: toasters@teaparty.net
Subject: RE: Is there a graph somewhere of performance vs raid group
size?
> On Mon, 31 Oct 2011, Cotton, Randall wrote:Well, I simply don't have enough disks yet to fill up a single raid
> > Just to clarify: for me, raid group size = aggregate size - that is,
> > I'll only have one raid group per aggregate.
> I'm curious about this statement. Any reason why? What exactly is it
that you are trying to accomplish?
group per node. 80 disks, 6 nodes.
Sure, no doubt, but if I can save, say, 3 or 4 disks that I can use in
> I may not have answers to rg size vs. performance, but I can tell you
that if you limit the sizes of your aggregates, performance *will*
suffer in almost every case.
any of my 6 nodes some time in the future by making my aggregate 12 or
13 disks instead of 16, and I only lose, say, 10% performance potential
by doing so, it will make sense for us.
Right, though I understand from conventional wisdom that the gains
> While you'll start seeing benefits of striping almost immediately, you
won't get real gains for a full data center until you have many, many
disks sharing the I/O load.
diminish to tiny increments past about 16 data disks per aggregate (and
your exposure to a failed disk and long reconstruction times becomes big
enough that going past 16 may not be worth it).
Well said. I'll go down that road, certainly.
> The thing is, it's in the vendor's best interests to help you
configure the units in a way that they perform well and meet your needs.
Granted the vendor also wants to sell more hardware and more disks, but
it's worth working with them and getting white papers about it.
Thanks,
Randall
_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters