Even if you are connecting the client to one running node, it will just act as 
co-coordinator , the read write/read will ends in the actual node where the 
data exists.
 
Bu multithread, I mean non serialized read/write (read or write , one after 
another). If this is the case then surely ur equation is right. ( throughput is 
proportional to latency)
 
Thanks & Regards
Job M Thomas 
Platform & Technology
Mob : 7560885748

________________________________

From: Ajay [mailto:ajay.ga...@gmail.com]
Sent: Fri 12/26/2014 12:52 PM
To: user@cassandra.apache.org
Subject: Re: Throughput Vs Latency


Hi Thomas,


I am little confused when you say multithreaded client. Actually we don't 
explicitly invoke read on multiple servers (for replicated data) from the 
client code. So how does multithreaded client fix this?


Thanks

Ajay



On Fri, Dec 26, 2014 at 12:08 PM, Job Thomas <j...@suntecgroup.com> wrote:


        Hi Ajay,
        
        My understanding is this,If you have a cluster of 3 nodes with 
replication factor of 3 , then the latency has more roll in throughput.
        
        It the cluster size is 6 with replication factor or 3 and if  you are 
using multithreaded client, then the latency remain same and you will get 
better throughput.(Not because of 6 node but because of 6 nodes and multiple 
threads).
        
        Thanks & Regards
        Job M Thomas
        Platform & Technology
        Mob : 7560885748
        
        ________________________________
        
        From: Ajay [mailto:ajay.ga...@gmail.com]
        Sent: Fri 12/26/2014 11:57 AM
        To: user@cassandra.apache.org
        Subject: Re: Throughput Vs Latency
        


        Thanks Thomas for the clarification.
        
        
        If I use the Consistency level of QUORUM for Read and Write, the 
Latency would affect the Throughput right?
        
        
        Thanks
        
        Ajay
        
        
        On Fri, Dec 26, 2014 at 11:15 AM, Job Thomas <j...@suntecgroup.com> 
wrote:
        
        
                Hi,
        
                First of all,the write latency of cassandra is not high(Read is 
high).
        
                The high throughput is achieved through distributes read and 
write.
        
                Your doubt ( If Latency is more how come the Throughput is high 
) is some what right if you put high consistency to both read and write.
        
                You will get distributed abilities since it is not Master/Slave 
architecture(Like HBase).
        
                 If  your consistency is lesser,then some nodes out of all 
replica nodes are free and will be used for another read/write . [ Think you 
are using multithreaded
                application ]
        
                Thanks & Regards
                Job M Thomas
                Platform & Technology
                Mob : 7560885748
        
        ________________________________
        
                From: Ajay [mailto:ajay.ga...@gmail.com]
                Sent: Fri 12/26/2014 10:46 AM
                To: user@cassandra.apache.org
                Subject: Throughput Vs Latency
        
        
                Hi,
        
        
                I am new to No SQL (and Cassandra). As I am going through few 
articles on Cassandra, it says Cassandra achieves highest throughput among 
various No SQL solutions but at the cost of high  read and write latency. I 
have a basic question here - (If my understanding is right) Latency means the 
time taken to accept input, process and respond back. If Latency is more how 
come the Throughput is high?
        
        
                Thanks
        
                Ajay
        
        
        
        


<<winmail.dat>>

Reply via email to