MySQL Forums
Forum List  »  NDB clusters

scaling OLTP
Posted by: Michael Moores
Date: July 18, 2005 01:20PM

My question regards the scalability of update/insert operations across
a cluster. My background is with Oracle, and I know that with Oracle RAC you can't scale much beyond 4-5 nodes because of the data synchronization overhead between nodes. Maintaining read consistency across nodes can be very expensive when the data is dirtied by one node and then
queried again by another node.

If I intend to scale Oracle RAC beyond a few nodes, we would partition the requests based on a partition key, instead of spraying requests randomly across nodes. So we would essentially force each node to cache a known parition of data in memory.
This results in inserts/updates and queries being directed to a particular pair of nodes (one primary and one failover), and this dramatically reduces data contention across the network when multiple nodes have copies of the same data in cache. Oracle asserts that we can scale for beyond a few nodes if we take this approach.

Should I consider the same approach with MySQL cluster?
What should I be thinking about here if I want to consider MySQL cluster?

Thanks,
--Michael

Options: ReplyQuote


Subject
Views
Written By
Posted
scaling OLTP
2773
July 18, 2005 01:20PM
1779
July 18, 2005 04:03PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.