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
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
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
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
Hi Matija,
Your experience mirrors ours. Can you please share any lessons learned or
suggestions you might have ?
We are using CMS because that is the default setting that came with 3.0.9. We
had read that G1 was supposed to be the default seeing in 3.0 but the following
links made it seem as
