"user@cassandra.apache.org" <user@cassandra.apache.org>
Date: Sunday, January 8, 2017 at 8:01 PM
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Cc: Abhishek Kumar Maheshwari <abhishek.maheshw...@timesinternet.in>
Subject: Re: Cassandra cluster perfo
apache.org" <user@cassandra.apache.org>
> *Date: *Friday, January 6, 2017 at 6:05 AM
> *To: *"user@cassandra.apache.org" <user@cassandra.apache.org>
> *Cc: *Abhishek Kumar Maheshwari <abhishek.maheshw...@timesinternet.in>
>
>
> *Subject: *Re: Cassandr
rceId TEXT," +
"nextId TEXT," +
"prevId TEXT," +
"PRIMARY KEY ((parentResourceId), childName)" +
")";
From: Abhishek Kumar Maheshwari
<abhishek.maheshw...@timesinternet.in<mailto:abhishek.maheshw...@timesintern
*"parentId TEXT," *+
>> *")"*;
>>
>> *"CREATE TABLE IF NOT EXISTS onem2m.Children_" *+ i + *"(" *+
>> *"parentResourceId TEXT," *+
>> *"childName TEXT," *+
>> *"
uot;CREATE TABLE IF NOT EXISTS onem2m.Children_" *+ i + *"(" *+
> *"parentResourceId TEXT," *+
> *"childName TEXT," *+
> *"childResourceId TEXT," *+
> *"nextId TEXT," *+
> *"prevI
t;nextId TEXT," +
"prevId TEXT," +
"PRIMARY KEY ((parentResourceId), childName)" +
")";
From: Abhishek Kumar Maheshwari <abhishek.maheshw...@timesinternet.in>
Date: Sunday, December 25, 2016 at 8:54 PM
To: "Branislav Janosik -T (bjano
Hi,
No we are not using async writes.
From: kurt Greaves <k...@instaclustr.com>
Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Date: Friday, December 23, 2016 at 12:17 AM
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Subj
tely necessary. Spread
environmental awareness.
From: Branislav Janosik -T (bjanosik - AAP3 INC at Cisco)
[mailto:bjano...@cisco.com]
Sent: Thursday, December 22, 2016 6:18 AM
To: user@cassandra.apache.org
Subject: Re: Cassandra cluster performance
Hi,
- Consistency level is set to ONE
- Keys
Branislav, are you doing async writes?
t;user@cassandra.apache.org" <user@cassandra.apache.org>
Subject: Re: Cassandra cluster performance
Given you’re using replication factor 1 (so each piece of data is only going to
get written to one node) something definitely seems wrong. Some questions/ideas:
- are there any errors in th
;
>
>
>
>
>
>
> *From: *Ben Slater <ben.sla...@instaclustr.com>
> *Reply-To: *"user@cassandra.apache.org" <user@cassandra.apache.org>
> *Date: *Wednesday, December 21, 2016 at 2:32 PM
> *To: *"user@cassandra.apache.org" <user@cassand
t; <user@cassandra.apache.org>
Date: Wednesday, December 21, 2016 at 2:32 PM
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Subject: Re: Cassandra cluster performance
You would expect some drop when moving to single multiple nodes but on the face
of it that feels
You would expect some drop when moving to single multiple nodes but on the
face of it that feels extreme to me (although I’ve never personally tested
the difference). Some questions that might help provide an answer:
- what consistency level are you using for the test?
- what is your keyspace
Hi all,
I’m working on a project and we have Java benchmark test for testing the
performance when using Cassandra database. Create operation on a single node
Cassandra cluster is about 15K operations per second. Problem we have is when I
set up cluster with 2 or more nodes (each of them are on
14 matches
Mail list logo
