Skip to main content

Timeline for MySQL Sharding vs MySQL Cluster

Current License: CC BY-SA 3.0

8 events
when toggle format what by license comment
S Sep 7, 2015 at 8:26 history suggested nhahtdh CC BY-SA 3.0
Minor formatting
Sep 7, 2015 at 8:11 review Suggested edits
S Sep 7, 2015 at 8:26
Dec 19, 2011 at 16:59 comment added Frazer Clement Hi Rolando, Thanks for clarifying your statements. It's true that non-pruned ordered index scans are 'expensive' in Cluster, as all data nodes are involved. It sounds like these scans on low cardinality indices would be expensive on any system, but on Cluster they became visibly expensive. Your caution and pessimism have no doubt saved you more than once :) Thanks for the +1
Dec 8, 2011 at 16:59 comment added RolandoMySQLDBA In lieu of my ranting and raving, +1 for your answer !!!
Dec 8, 2011 at 16:57 comment added RolandoMySQLDBA In your link, it mentioned 'an ordered index scan' that could not be pruned, as matching rows are not guaranteed to be stored in one table fragment. This is why I was suggesting isolating data to specfic shards (data nodes) to minimize the places data would spread. Since your answer brings out the positive side of MySQL Cluster, it better fits the original posted question. My answer errs in favor of caution, pessimism, and being somewhat naive of MySQL Cluster power today.
Dec 8, 2011 at 16:50 comment added RolandoMySQLDBA Hey, Frazier. I read the link you provided. Just for claraification, my 'compound key' comment was based on non-unique indexes. My employer's company tried out MySQL Cluster around 2007 Q1 and did not like it because of poor performance. IMHO it was the client's poor choices for keys (small cardinalities) and his queries. MySQL Cluster must have matured more since then based on your link. As to my second statement, this is how many MongoDB users populate specific shards. Some of my employer's clients have done this with their custom MySQL setups.
Dec 8, 2011 at 14:49 vote accept gsb
Dec 8, 2011 at 14:08 history answered Frazer Clement CC BY-SA 3.0