Re: replication impact on write throughput

2010-05-12 Thread Mark Greene
>>If the replication factor is 2, then everything is written twice. So >>your throughput is cut in half. throughput of new inserts is cut in half right? I think I was thinking about capacity in more general terms from the node's perspective. The node has the ability to write so many operations per

Re: replication impact on write throughput

2010-05-12 Thread David Vanderfeesten
About this linear scaling of throughput(with keys perfectly distributed + requests balanced over all nodes): I would assume that this is not the case for small number of nodes because starting from 2 nodes onwards a part of the requests have to be handled by a proxy node + the actual node responsib

Re: replication impact on write throughput

2010-05-11 Thread Paul Prescod
On Tue, May 11, 2010 at 5:56 PM, Mark Greene wrote: > I was under the impression from what I've seen talked about on this list > (perhaps I'm wrong here) that given the write throughput of one node in a > cluster (again assuming each node has a given throughput and the same > config) that you woul

Re: replication impact on write throughput

2010-05-11 Thread Mark Greene
I was under the impression from what I've seen talked about on this list (perhaps I'm wrong here) that given the write throughput of one node in a cluster (again assuming each node has a given throughput and the same config) that you would simply multiply that throughput by the number of nodes you

Re: replication impact on write throughput

2010-05-11 Thread Jonathan Ellis
On Tue, May 11, 2010 at 11:10 AM, Bill de hOra wrote: > I know this is highly simplified take on things (ie no consideration for > reads or quorum), I'm just trying to understand what the implication of > replication is on write scalability. Intuitively it would seem actual write > capacity is tot

Re: replication impact on write throughput

2010-05-11 Thread Bill de hOra
Mark Greene wrote: If you have for example, your replication factor equal to the total amount of nodes in the ring, I suspect you will hit a brick wall pretty soon. Right :) So if we said there was 100 nodes at 5K wps with R=2, then would that suggest the cluster can support 250K wps? Again

Re: replication impact on write throughput

2010-05-11 Thread Peter Schüller
> The biggest impact on your write performance will most likely be the > consistency level of your writes. In other words, how many nodes you want to > wait for before you acknowledge the write back to the client. I believe the consistency level is only expected to have a significant impact on lat

Re: replication impact on write throughput

2010-05-11 Thread Mark Greene
If you have for example, your replication factor equal to the total amount of nodes in the ring, I suspect you will hit a brick wall pretty soon. The biggest impact on your write performance will most likely be the consistency level of your writes. In other words, how many nodes you want to wait f

replication impact on write throughput

2010-05-11 Thread Bill de hOra
If I had 10 Cassandra nodes each with a write capacity of 5K per second and a replication factor of 2, would that mean the expected write capacity of the system would be ~25K writes per second because the nodes are also serving other nodes and not just clients? I know this is highly simplified