g) to handle large queries, or
>> maybe simple, Cassandra-style “horizontal scaling” (adding nodes) will be
>> sufficient. Sure, you can tune Cassandra for single-node performance, but
>> that seems lot a lot of extra work, to me, compared to adding more cheap
>> nodes
t; nodes.
>
> -- Jack Krupansky
>
> *From:* Diane Griffith
> *Sent:* Thursday, July 17, 2014 9:31 AM
> *To:* user
> *Subject:* Re: trouble showing cluster scalability for read performance
>
> Duncan,
>
> Thanks for that feedback. I'll give a bit more info and the
tune Cassandra for single-node performance, but that seems lot a
lot of extra work, to me, compared to adding more cheap nodes.
-- Jack Krupansky
From: Diane Griffith
Sent: Thursday, July 17, 2014 9:31 AM
To: user
Subject: Re: trouble showing cluster scalability for read performance
Duncan
Duncan,
Thanks for that feedback. I'll give a bit more info and then ask some more
questions.
*Our Goal*: Not to produce the fastest read but show horizontal scaling.
*Test procedure*:
* Inserted 54M rows where one third of that represents a unique key, 18M
keys. End result given our schema i
Hi Diane,
On 17/07/14 06:19, Diane Griffith wrote:
We have been struggling proving out linear read performance with our cassandra
configuration, that it is horizontally scaling. Wondering if anyone has any
suggestions for what minimal configuration and approach to use to demonstrate
this.
We
We have been struggling proving out linear read performance with our
cassandra configuration, that it is horizontally scaling. Wondering if
anyone has any suggestions for what minimal configuration and approach to
use to demonstrate this.
We were trying to go for a simple set up, so on the keyspa
