cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Greene <green...@gmail.com>
Subject Re: replication impact on write throughput
Date Wed, 12 May 2010 12:45:42 GMT
>>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 second whether that be a replicated
key or not and you could potentially take that number and multiply it by the
number of nodes in the ring to give you your write capacity per second.

On Tue, May 11, 2010 at 10:13 PM, Paul Prescod <paul@prescod.net> wrote:

> On Tue, May 11, 2010 at 5:56 PM, Mark Greene <greenemj@gmail.com> 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 would simply multiply that throughput by the number of
> > nodes you had, giving you the total throughput for the entire ring (like
> you
> > said this is somewhat artificial). The main benefit being that adding
> > capacity was as simple as adding more nodes to the ring with no
> degradation.
> > So by your math, 100 nodes with each node getting 5k wps, I would assume
> the
> > total capacity is 500k wps. But perhaps I've misunderstood some key
> > concepts. Still a novice myself ;-)
>
> If the replication factor is 2, then everything is written twice. So
> your throughput is cut in half.
>
>  Paul Prescod
>

Mime
View raw message