Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2017-05-04 Thread techpyaasa .
; Its really very useful >> >> Same can be be done in a normal situation to compare the difference. >> >> That should give more insights. >> >> Cheers, Corry >> >> >> Op vrijdag 29 januari 2016 heeft Peddi, Praveen het >> volgende geschreve

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-11-08 Thread Dikang Gu
gnificantly. However, 2.1.11 > read latencies are still 1.5 slower than 2.0.9. One thing we noticed in JMX > metric that could affect read latencies is that 2.1.11 is running > ReadRepairedBackground and ReadRepairedBlocking too frequently compared to > 2.0.9 even though our read_repair_chan

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-10-28 Thread Paulo Motta
er, 2.1.11 read latencies are still 1.5 >>>>> slower >>>>> than 2.0.9. One thing we noticed in JMX metric that could affect read >>>>> latencies is that 2.1.11 is running ReadRepairedBackground and >>>>> ReadRepairedBlocking too frequently comp

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-10-28 Thread Dikang Gu
> Date: Thursday, January 14, 2016 at 2:58 PM >>>> To: "user@cassandra.apache.org" >>>> Subject: Re: Slow performance after upgrading from 2.0.9 to 2.1.11 >>>> >>>> Sorry I wasn’t as explicit as I should have been >>>&g

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-29 Thread Corry Opdenakker
;>> dclocal_read_repair_chance=0.10 AND >>> read_repair_chance=0.00 AND >>> >>> Here is the table for read repair metrics for both clusters. >>> 2.0.9 2.1.11 >>> ReadRepairedBackground 5MinAvg 0.006 0.1 >>> 15MinAvg 0.009 0.153 >>&

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-29 Thread Jean Carlo
gt; 2.0.9 2.1.11 >> ReadRepairedBackground 5MinAvg 0.006 0.1 >> 15MinAvg 0.009 0.153 >> ReadRepairedBlocking 5MinAvg 0.002 0.55 >> 15MinAvg 0.007 0.91 >> >> Thanks >> Praveen >> >> From: Jeff Jirsa >> Reply-To: >> Date: Thursday, Janua

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-29 Thread Peddi, Praveen
...@thelastpickle.com>> Reply-To: Cassandra Users mailto:user@cassandra.apache.org>> Date: Friday, January 29, 2016 at 3:01 PM To: Cassandra Users mailto:user@cassandra.apache.org>> Subject: Re: Slow performance after upgrading from 2.0.9 to 2.1.11 On Fri, Jan 29, 2016 at 12:30

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-29 Thread Corry Opdenakker
Reply-To: > > Date: Thursday, January 14, 2016 at 2:58 PM > To: "user@cassandra.apache.org > " < > user@cassandra.apache.org > > > Subject: Re: Slow performance after upgrading from 2.0.9 to 2.1.11 > > Sorry I wasn’t as explicit as I should have been > > Th

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-29 Thread Nate McCall
On Fri, Jan 29, 2016 at 12:30 PM, Peddi, Praveen wrote: > > Hello, > We have another update on performance on 2.1.11. compression_chunk_size didn’t really help much but We changed concurrent_compactors from default to 64 in 2.1.11 and read latencies improved significantly. However, 2.1.11 read la

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-29 Thread Peddi, Praveen
e.org<mailto:user@cassandra.apache.org>" mailto:user@cassandra.apache.org>> Subject: Re: Slow performance after upgrading from 2.0.9 to 2.1.11 Sorry I wasn’t as explicit as I should have been The same buffer size is used by compressed reads as well, but tuned with compression_chunk_size tab

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-14 Thread Jeff Jirsa
re:Invent youtube link I sent in my original reply. From: "Peddi, Praveen" Reply-To: "user@cassandra.apache.org" Date: Thursday, January 14, 2016 at 11:36 AM To: "user@cassandra.apache.org", Zhiyan Shao Cc: "Agrawal, Pratik" Subject: Re: Slow performance

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-14 Thread Peddi, Praveen
t; Cc: "Agrawal, Pratik" mailto:paagr...@amazon.com>> Subject: Re: Slow performance after upgrading from 2.0.9 to 2.1.11 This may be due to https://issues.apache.org/jira/browse/CASSANDRA-10249 / https://issues.apache.org/jira/browse/CASSANDRA-8894 - whether or not this is really the

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-14 Thread Jeff Jirsa
significantly speeds up read workloads for us. From: Zhiyan Shao Date: Thursday, January 14, 2016 at 9:49 AM To: "user@cassandra.apache.org" Cc: Jeff Jirsa, "Agrawal, Pratik" Subject: Re: Slow performance after upgrading from 2.0.9 to 2.1.11 Praveen, if you search "Read is sl

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-14 Thread Zhiyan Shao
adCount WRITE 33220 4453 4453 4453 3.5 3.2 5.7 8.2 36.8 68 7.5 54 > threadCount total 10 13404 13404 13404 4 3.7 6.6 9.2 48 69.9 7.5 > > From: Jeff Jirsa > Date: Thursday, January 7, 2016 at 1:01 AM > To: "user@cassandra.apache.org" , Peddi > Praveen > Subject:

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-12 Thread Peddi, Praveen
"user@cassandra.apache.org<mailto:user@cassandra.apache.org>" mailto:user@cassandra.apache.org>>, Peddi Praveen mailto:pe...@amazon.com>> Subject: Re: Slow performance after upgrading from 2.0.9 to 2.1.11 Anecdotal evidence typically agrees that 2.1 is faster than 2.0 (our e

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-06 Thread Jeff Jirsa
est (that’d be unusual)? Are you doing a lot of compaction? From: "Peddi, Praveen" Reply-To: "user@cassandra.apache.org" Date: Wednesday, January 6, 2016 at 11:41 AM To: "user@cassandra.apache.org" Subject: Slow performance after upgrading from 2.0.9 to 2.1.11 Hi

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-06 Thread Peddi, Praveen
Hi Michael, I am not comparing my results with results on that page. I mentioned only in the context of improved performance in 2.1 compared to 2.0. That page compares performance between 2.0 and 2.1 with same hardware. I am doing the same exact thing (running 2.0.9 and 2.1.11 on same hardware,

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-06 Thread Michael Shuler
On 01/06/2016 03:57 PM, Peddi, Praveen wrote: > This blog > > claims Cassandra is now 50% faster. We are obviously not seeing that. That post compared cassandra-stress write on versions 2.0 and 2.1, each on a single AWS c3.8xlarge

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-06 Thread Peddi, Praveen
day, January 6, 2016 at 3:49 PM To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" mailto:user@cassandra.apache.org>> Subject: Re: Slow performance after upgrading from 2.0.9 to 2.1.11 On Wed, Jan 6, 2016 at 11:49 AM, Peddi, Praveen mailto:pe...@amazon.com&

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-06 Thread Robert Coli
On Wed, Jan 6, 2016 at 11:49 AM, Peddi, Praveen wrote: > 2nd column is replication factor (RF). I have 2 rows for reads and 2 for > writes. First row is RF=1 and 2nd row is RF=3. So when I said increasing RF > , I meant from 1 to 3. Sorry the table is probably not clear. > Ah, I see now, I was m

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-06 Thread Peddi, Praveen
"user@cassandra.apache.org<mailto:user@cassandra.apache.org>" mailto:user@cassandra.apache.org>> Date: Wednesday, January 6, 2016 at 2:44 PM To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" mailto:user@cassandra.apache.org>> Subject: Re: Slo

Re: Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-06 Thread Robert Coli
On Wed, Jan 6, 2016 at 11:41 AM, Peddi, Praveen wrote: > We have upgraded Cassandra from 2.0.9 to 2.1.11 in our loadtest > environment with pretty much same yaml settings in both (removed unused > yaml settings and renamed few others) and we have noticed performance on > 2.1.11 is worse compared

Slow performance after upgrading from 2.0.9 to 2.1.11

2016-01-06 Thread Peddi, Praveen
Hi, We have upgraded Cassandra from 2.0.9 to 2.1.11 in our loadtest environment with pretty much same yaml settings in both (removed unused yaml settings and renamed few others) and we have noticed performance on 2.1.11 is worse compared to 2.0.9. After more investigation we found that the perfo