>
> FC - 6, Sector 16A, Film City, Noida, U.P. 201301 | INDIA
>
> *P** Please do not print this email unless it is absolutely necessary.
> Spread environmental awareness.*
>
>
>
> *From:* Benjamin Roth [mailto:benjamin.r...@jaumo.com]
> *Sent:* Wednesday, November 23, 2016 4:09
.
From: Benjamin Roth [mailto:benjamin.r...@jaumo.com]
Sent: Wednesday, November 23, 2016 4:09 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra Config as per server hardware for heavy write
This has nothing to do with sync/async operations. An async operation is also
replayable
nvironmental awareness.
From: Vladimir Yudovin
[mailto:vla...@winguzone.com<mailto:vla...@winguzone.com>]
Sent: Wednesday, November 23, 2016 3:47 PM
To: user <user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
Subject: RE: Cassandra Config as per server hardware for he
areness.*
>
>
>
> *From:* Vladimir Yudovin [mailto:vla...@winguzone.com]
> *Sent:* Wednesday, November 23, 2016 3:47 PM
> *To:* user <user@cassandra.apache.org>
> *Subject:* RE: Cassandra Config as per server hardware for heavy write
>
>
>
> session.execute is comi
awareness.
From: Vladimir Yudovin
[mailto:vla...@winguzone.com<mailto:vla...@winguzone.com>]
Sent: Wednesday, November 23, 2016 3:15 PM
To: user <user@cassandra.apache.org<mailto:user@cassandra.apache.org>>
Subject: RE: Cassandra Config as per server hardware for heavy write
To: user user@cassandra.apache.org
Subject: RE: Cassandra Config as per server hardware for heavy write
I have a list with 1cr record. I am just iterating on it and executing the
query. Also, I try with 200 thread
Do you fetch each list item and put it to separate thread to perform CQL
r <user@cassandra.apache.org>
Subject: RE: Cassandra Config as per server hardware for heavy write
>I have a list with 1cr record. I am just iterating on it and executing the
>query. Also, I try with 200 thread
Do you fetch each list item and put it to separate thread to perform CQL query?
Also
...@gmail.com]
Sent: Wednesday, November 23, 2016 2:23 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra Config as per server hardware for heavy write
Hi Abhishek,
You could check whether you are throttling on client side queries or on
cassandra side.
You could also use grafana to monitor
29.l...@gmail.com]
Sent: Wednesday, November 23, 2016 2:23 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra Config as per server hardware for heavy write
Hi Abhishek,
You could check whether you are throttling on client side queries or on
cassandra side.
You could also use grafana to mon
IA
P Please do not print this email unless it is absolutely necessary. Spread
environmental awareness.
From: Vladimir Yudovin [mailto:vla...@winguzone.com]
Sent: Wednesday, November 23, 2016 2:07 PM
To: user <user@cassandra.apache.org>
Subject: RE: Cassandra Config as per server hardware for h
necessary. Spread
environmental awareness.
From: Vladimir Yudovin [mailto:vla...@winguzone.com]
Sent: Wednesday, November 23, 2016 2:00 PM
To: user user@cassandra.apache.org
Subject: RE: Cassandra Config as per server hardware for heavy write
I have 1Cr records in my Java ArrayList
read
environmental awareness.
From: Vladimir Yudovin [mailto:vla...@winguzone.com]
Sent: Wednesday, November 23, 2016 2:00 PM
To: user <user@cassandra.apache.org>
Subject: RE: Cassandra Config as per server hardware for heavy write
>I have 1Cr records in my Java ArrayList and yes I am writing in sync
To: user@cassandra.apache.org
Subject: Re: Cassandra Config as per server hardware for heavy write
This is ridiculously slow for that hardware setup. Sounds like you benchmark
with a single thread and / or sync queries or very large writes.
A setup like this should be easily able to
ENTILE';
>
>
>
> So please let me know what I miss?
>
>
>
> And for this hardware below config is fine?
>
>
>
> concurrent_reads: 32
>
> concurrent_writes: 64
>
> concurrent_counter_writes: 32
>
> compaction_throughput_mb_per_sec: 32
>
> c
writes: 64
concurrent_counter_writes: 32
compaction_throughput_mb_per_sec: 32
concurrent_compactors: 8
thanks,
Abhishek
From: Benjamin Roth [mailto:benjamin.r...@jaumo.com]
Sent: Wednesday, November 23, 2016 12:56 PM
To: user@cassandra.apache.org
Subject: Re: Cassandra Config as per server hardware for heavy write
Thi
This is ridiculously slow for that hardware setup. Sounds like you
benchmark with a single thread and / or sync queries or very large writes.
A setup like this should be easily able to handle tens of thousands of
writes / s
2016-11-23 8:02 GMT+01:00 Jonathan Haddad :
> How
How are you benchmarking that?
On Tue, Nov 22, 2016 at 9:16 PM Abhishek Kumar Maheshwari <
abhishek.maheshw...@timesinternet.in> wrote:
> Hi,
>
>
>
> I have 8 servers in my Cassandra Cluster. Each server has 64 GB ram and 40
> Cores and 8 SSD. Currently I have below config in Cassandra.yaml:
>
>
17 matches
Mail list logo