incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: Performance thoughts on CQL
Date Sat, 07 May 2011 18:13:06 GMT
The only "query planning" Cassandra does is deciding which index to
use when there are multiple options. That is handled the same way
whether the request is from CQL or classic Thrift.

On Sat, May 7, 2011 at 8:17 AM, Edward Capriolo <edlinuxguru@gmail.com> wrote:
> Having used mysql as key value store before I have noticed that when
> doing low-latency queries the query planning time can actually end up
> being larger then the execution time. Even if you use a prepared
> statement mechanism with clients connecting and disconnecting this can
> be a lot of overhead. Will CQL prepare statements on the client or the
> server side? How does CQL perform against get_slice when a read comes
> from pure row cache?
>
> Edward
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Mime
View raw message