Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: 64 node Oracle RAC Cluster (The reality of...)

RE: 64 node Oracle RAC Cluster (The reality of...)

From: Mark W. Farnham <mwf_at_rsiz.com>
Date: Tue, 21 Jun 2005 12:56:02 -0400
Message-ID: <KNEIIDHFLNJDHOOCFCDKOEMLGIAA.mwf@rsiz.com>


The difference is that any node in the RAC can acquire the various blocks you need, and you don't HAVE TO partition functionally.

However, if you route all the clients, say, using the Accounts Payables client software to a particular instance, then the vast majority of blocks they need will be in the instance they are running on.

This will tend to greatly reduce the heat on the internode connection fabric, leaving headroom for things that don't functionally partition so neatly.

But all instances CAN see all the data and you use one of several failover strategies if the preferred node for a particular functional partition goes off line.

While I generally favor staying toward the bigger SMP/NUMA with fewer nodes side of the trade-off slope versus many-noded small box RAC (based on constant dollars and highest reliability to serve a given functional requirement), Oracle's architecture for RAC/GRID is clearly very good.

Regards,

mwf

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Jesse, Rich Sent: Tuesday, June 21, 2005 12:45 PM
To: oracle-l_at_freelists.org
Subject: RE: 64 node Oracle RAC Cluster (The reality of...)

Hey Mladen,

Just for my own clarity, how does functional partitioning differ from SQueaLServer's federated layout? I remember an Oracle Marketing Schpeel about how that was a bad thing when compared to RAC, specifically targeting the high TPC marks (which in themselves are irrelevant). The bad part being the SPOF of any one box in the federated cluster would take out that functionality being solely hosted on that one box.

TIA,
Rich

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Mladen Gogala Sent: Tuesday, June 21, 2005 8:20 AM
To: cmarquez_at_collegeboard.org
Cc: rjamya; oracle-l_at_freelists.org
Subject: Re: 64 node Oracle RAC Cluster (The reality of...)

On 06/21/2005 08:17:38 AM, Marquez, Chris wrote:
> >>thought of seeing eye popping
> >>number of 'global cache cr requests'
> >>for a 64 node RAC gives me chills.
>
> My thoughts exactly!
>
> Chris Marquez
> Oracle DBA
>

There are two unholy words which Oracle sales people usually avoid when talking
about RAC: functional partitioning. Functional partitioning means that each RAC
node has a separate and specialized function and is mostly dealing with one part
the database. That is still the best way of organizing RAC system. Also, with
several cluster nodes, the private connection becomes crucial. With 64 nodes,
N-cube like communication structure must be in place, so that each node is
reachable through the fixed number of hops.

--
Mladen Gogala
Oracle DBA


--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l
Received on Tue Jun 21 2005 - 13:02:39 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US