is absolutely necessary.
> Spread environmental awareness.*
>
>
>
> *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
&
environmental awareness.
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 oper
to:vla...@winguzone.com>]
Sent: Wednesday, November 23, 2016 3:47 PM
To: user mailto:user@cassandra.apache.org>>
Subject: RE: Cassandra Config as per server hardware for heavy write
session.execute is coming from Session session = cluster.connect(); I guess?
So actually all threads work w
areness.*
>
>
>
> *From:* Vladimir Yudovin [mailto:vla...@winguzone.com]
> *Sent:* Wednesday, November 23, 2016 3:47 PM
> *To:* user
> *Subject:* RE: Cassandra Config as per server hardware for heavy write
>
>
>
> session.execute is coming from Session session = cluste
lto:vla...@winguzone.com>]
Sent: Wednesday, November 23, 2016 3:15 PM
To: user mailto: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
mber 23, 2016 3:15 PM
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
it is absolutely necessary. Spread
environmental awareness.
From: siddharth verma
[mailto:sidd.verma29.l...@gmail.com<mailto:sidd.verma29.l...@gmail.com>]
Sent: Wednesday, November 23, 2016 2:23 PM
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: Re: Cassandra Config as pe
lto:sidd.verma29.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 a
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 monitor
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
Subject: RE: Cassandra Config as per server hardware for heavy write
So do you see speed w
nless it is absolutely necessary.
> Spread environmental awareness.*
>
>
>
> *From:* Vladimir Yudovin [mailto:vla...@winguzone.com]
> *Sent:* Wednesday, November 23, 2016 2:00 PM
> *To:* user
> *Subject:* RE: Cassandra Config as per server hardware for heavy write
>
&g
absolutely 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 i
read
environmental awareness.
From: Vladimir Yudovin [mailto:vla...@winguzone.com]
Sent: Wednesday, November 23, 2016 2:00 PM
To: user
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 mode.
Is your Java program
amin 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
This is ridiculously slow for that hardware setup. Sounds like you benchmark
with a single thread and / or
chance = 0.0
>
> AND speculative_retry = '99.0PERCENTILE';
>
>
>
> So please let me know what I miss?
>
>
>
> And for this hardware below config is fine?
>
>
>
> concurrent_reads: 32
>
> concurrent_writes: 64
>
> concurrent_counter
this hardware below config is fine?
concurrent_reads: 32
concurrent_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
Sub
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 are you benchmarking th
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:
>
>
>
18 matches
Mail list logo
