Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of nate@datastax.com designates
 209.85.210.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4E038A5D.8040203@gmail.com>
References: <BANLkTimqkZgp36uH9q98PSXm9CjjwX__uA@mail.gmail.com>
	<BANLkTin4aafN8igg=uNifCBug4p0mi1idg@mail.gmail.com>
	<BANLkTimWw0VzVK0mXmOmCzJ4xB1Ej366Qw@mail.gmail.com>
	<4E038A5D.8040203@gmail.com>
Date: Thu, 23 Jun 2011 14:00:58 -0500
Message-ID: <BANLkTiko_-eEW+yfhRSNMxK11nV7bzoYkw@mail.gmail.com>
Subject: Re: 99.999% uptime - Operations Best Practices?
From: Nate McCall <nate@datastax.com>
To: user@cassandra.apache.org
Cc: Les Hazlewood <les@katasoft.com>
Content-Type: text/plain; charset=ISO-8859-1

As an additional concrete detail to Edward's response, 'result
pinning' can provide some performance improvements depending on
topology and workload. See the conf file comments for details:
https://github.com/apache/cassandra/blob/cassandra-0.8.0/conf/cassandra.yaml#L308-315

I would also advise to take the time to experiment with consistency
levels (particularly in multi-DC setup) and their effect on response
times and weigh those against your consistency requirements.

For the record, any performance twiddling will only provide useful
results when comparable metrics are available for the similar workload
(Les, it appears you have a good grasp of this already - just wanted
to re-iterate).