I'm not sure I follow exactly what you're saying. Would I be correct that
you're talking about splitting the DB across multiple arrays/controllers? I
don't really see any reason to do that. I would generally prefer to just
add more disks to the array.
A good controller and an array of 8+ SSD should be able to support most
anyone.
If you're big enough that such a setup still isn't enough iops, I'd look at
the Fusion IO stuff or one of the similar products, there are also SAN
solutions. Bring the IO to the DB not vice versa.
I wouldn't partition the DB unless it's so big that having a monolithic
volume isn't manageable.
On Thu, May 31, 2012 at 8:56 AM, Nancy Dornacker <nancy.dornacker@...
*John Driggers*
*High End Dev, System Design, Profit Drinking*
*
**:: 904.404.9233*
*:: waffqle@...*
*:: NO FAXES*
*
*
[Non-text portions of this message have been removed]
you're talking about splitting the DB across multiple arrays/controllers? I
don't really see any reason to do that. I would generally prefer to just
add more disks to the array.
A good controller and an array of 8+ SSD should be able to support most
anyone.
If you're big enough that such a setup still isn't enough iops, I'd look at
the Fusion IO stuff or one of the similar products, there are also SAN
solutions. Bring the IO to the DB not vice versa.
I wouldn't partition the DB unless it's so big that having a monolithic
volume isn't manageable.
On Thu, May 31, 2012 at 8:56 AM, Nancy Dornacker <nancy.dornacker@...
> wrote:--
> **
>
>
> Would you also setup the database to be mult-volume and spread across
> multiple logical SSD drives?
>
>
> [Non-text portions of this message have been removed]
>
>
>
*John Driggers*
*High End Dev, System Design, Profit Drinking*
*
**:: 904.404.9233*
*:: waffqle@...*
*:: NO FAXES*
*
*
[Non-text portions of this message have been removed]