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 <romainh...@yahoo.fr.invalid> wrote:
> 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, > Romain > Le Jeudi 2 février 2017 9h52, Benjamin Lerer < > benjamin.le...@datastax.com> a écrit : > > > 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 for us to > investigate and solve those problems. > > By helping us you will help yourselves. > > On Thu, Feb 2, 2017 at 9:38 AM, Matija Gobec <matija0...@gmail.com> wrote: > > > 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. > > Next to everything Jeff mentioned, is there any reason you have data on > all > > nodes and use QUORUM? > > Also, is there any reason you are not using G1 with 3.0? > > > > On Thu, Feb 2, 2017 at 6:28 AM, Jeff Jirsa <jji...@gmail.com> wrote: > > > > > 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 < > > shashank.jo...@ericsson.com> > > > wrote: > > > > > > > > We are seeing major performance issues with about 100 GB of data in > > > 3.0.9-E001. The exact same app runs very well in 2.1. > > > > > > > > > > > > > > > > It feels to us like something is wrong with our configuration because > > of > > > the severity of the issues. Thanks in advance for any recommendations > or > > > suggestions. > > > > > > > > > > > > > > > > Details: > > > > > > > > Size of data: 100 GB+ all in one table, with a simple schema, couple > > of > > > bigints and a double > > > > > > > > Cluster: 3 nodes with RF of 3 > > > > > > > > Client: App uses read and write CL of QUORUM and we have a lots of > > > timeouts due to inability to reach quorum > > > > > > > > Compaction: Leveled > > > > > > > > Nature of data usage: No updates/deletes, High reads, relatively low > > > writes > > > > > > > > > > > > > > > > > > > > > > > > JVM: > > > > > > > > Using CMS GC and around 8 GB of max heap > > > > > > > > > > > >
