appening. So we even tested with autocompaction turned off but did not see any
improvement.
Thank you for any insights.
-Original Message-
From: Matija Gobec [mailto:matija0...@gmail.com]
Sent: Thursday, February 02, 2017 12:39 AM
To: dev@cassandra.apache.org
Subject: Re: Performance i
Also, if you have been tracking your performance metrics in graph form
(before and after the upgrade), that would be extremely helpful.
On Thu, Feb 2, 2017 at 5:29 AM Romain Hardouin
wrote:
> Yes you should provide more context."Lots of timeouts": read? write?
> both?Did you run sstableupgrade? J
Yes you should provide more context."Lots of timeouts": read? write? both?Did
you run sstableupgrade? Java version ? (C* 3.0 requires Java 8u40 or later)What
is your data model? Lots of counters? Compression enabled on tables? "No
updates/deletes": no deletes but is there TTL on data?
etc.
Best
Guys,
If you really want us to improve the things you need to be a bit more
helpfull.
We have no clue of what are the problems or changes in preformance that you
see.
So, if you could provide more context and facts it would be great.
The more help and clarity you can provide, the easier it will be
We ran for months with the same highly tuned setup on 2.1 and once we
switched to 3.0.9 the performance with the same configuration was crap.
Leveled compaction but a bit more nodes. There are differences in how 2.1
and 3.0 work so I guess you need to revisit your cassandra.yaml and os
settings.
Ne
Can you quantify "major"?
Latency or throughput?
GC pauses?
What did you see before? What do you see now?
Do you have a stack dump?
--
Jeff Jirsa
> On Feb 1, 2017, at 4:23 PM, Shashank Joshi
> wrote:
>
> We are seeing major performance issues with about 100 GB of data in
> 3.0.9-E001. T
