Re: Query faster 10 times when stop on data node
When running with 2 data nodes, each data note processes all reads and writes for 1 of the 2 partitions; if the query needs data from both partitions then this means that both data nodes need to do part of the work and there needs to be passing of messages between them - this can mean extra latency.
When only 1 data node is running, it's the primary for both partitions (all of the data) and so no messaging is involved and so latency is reduced.
You can optimise for this by using a 'shard aware' design - this white paper:
http://www.mysql.com/why-mysql/white-papers/guide-to-optimizing-performance-of-the-mysql-cluster/
Andrew.
Subject
Views
Written By
Posted
1712
October 29, 2014 09:16PM
Re: Query faster 10 times when stop on data node
832
October 30, 2014 07:25AM
788
November 06, 2014 01:16AM
740
January 23, 2015 09:47AM
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.