I've seen similar slowdowns in 2.0 - roughly the same 15%.
For instance, http://i.imgur.com/Qi6oo62.png
That's a comparison of 1.2.6 to 2.0beta1. Ignore the lines that say
speculative_retry=95percentile and ALWAYS.
Default 1.2 beats Default 2.0 in overall operation time.
Bisecting the cause of
Unfortunately, -1 from me.
See CASSANDRA-6074 https://issues.apache.org/jira/browse/CASSANDRA-6074
On Fri, Sep 20, 2013 at 12:16 PM, Pavel Yaskevich pove...@gmail.com wrote:
+1
On Sep 20, 2013, at 5:55 AM, Gary Dusbabek gdusba...@gmail.com wrote:
+1
On Fri, Sep 20, 2013 at 4:39
I retract my -1 (for now, I can't reproduce CASSANDRA-6074.)
Sorry for the noise.
On Fri, Sep 20, 2013 at 8:15 PM, Ryan McGuire r...@datastax.com wrote:
Unfortunately, -1 from me.
See CASSANDRA-6074 https://issues.apache.org/jira/browse/CASSANDRA-6074
On Fri, Sep 20, 2013 at 12:16 PM
32G nodes. I'm not mucking with heap settings so it's using -Xms8023M
-Xmx8023M -Xmn1600M
Looks like the same bug to me, whether it's caused by the same thing as it
was originally doesn't really matter.
Can you add your steps to reproduce it there? I'll reopen the bug for you.
Thanks for the bug report!
On Wed, Apr 2, 2014 at 11:43 PM, Ji Cheng memol...@gmail.com wrote:
Hi,
I
Thanks Mikhail, I remember I fixed this in
ccmhttps://github.com/pcmanus/ccm/commit/2c19025dc51578f074b889ad4b78ac9e0625e715,
but then I forgot that cqlsh_tests wasn't using the ccm api for invoking
that.
On Tue, Apr 8, 2014 at 5:54 PM, Mikhail Stepura mikhail.step...@outlook.com
wrote:
I
I'd like to see some dev response to my notes on
CASSANDRA-6525https://issues.apache.org/jira/browse/CASSANDRA-6525,
but other than that dtests for 2.0 look good.
On Mon, Apr 14, 2014 at 2:32 PM, Pavel Yaskevich pove...@gmail.com wrote:
Can I push new release of the thrift-server before we
We actually have some jython tests for a few test suites we wanted to use
the java driver with: https://github.com/riptano/cassandra-dtest-jython
On Thu, May 22, 2014 at 2:36 PM, Jake Luciani jak...@gmail.com wrote:
Jython! :D
On Thu, May 22, 2014 at 12:09 PM, Benedict Elliott Smith
+1
On Sun, Aug 3, 2014 at 10:44 PM, Jake Luciani jak...@gmail.com wrote:
+1
On Saturday, August 2, 2014, Sylvain Lebresne sylv...@datastax.com
wrote:
I propose the following artifacts for release as 2.1.0-rc5. Unless
someone
strongly
object, we'll keep the vote period for this one
dtests looks good except for CASSANDRA-7281
https://issues.apache.org/jira/browse/CASSANDRA-7281, but looks like that
got pushed up to 2.0.13.
On Fri, Jan 9, 2015 at 5:34 PM, Jake Luciani j...@apache.org wrote:
I propose the following artifacts for release as 2.0.12.
sha1:
I'm taking notes from the infrastructure doc and wrote down some action
items for my team:
https://gist.github.com/EnigmaCurry/d53eccb55f5d0986c976
--
[image: datastax_logo.png] http://www.datastax.com/
Ryan McGuire
Software Engineering Manager in Test | r...@datastax.com
[image
://www.datastax.com/
Ryan McGuire
Software Engineering Manager in Test | r...@datastax.com
[image: linkedin.png] https://www.linkedin.com/in/enigmacurry [image:
twitter.png] http://twitter.com/enigmacurry
http://github.com/enigmacurry
+1, from a testing perspective we run dtest and unit tests on hotspot 8 and
openjdk 8 and have seen no problems.
On Thu, May 7, 2015 at 12:09 PM, Jonathan Ellis jbel...@gmail.com wrote:
We discussed requiring Java 8 previously and decided to remain Java
7-compatible, but at the time we were
In the meantime can we agree on having cassci to validate personal merged
branches before pushing either, in case of non-trunk patches?
+100 from me, but why the exception for trunk? Wouldn't it be easier to
wait for the dev branch tests to pass and then do all the merging at once
(2.0, 2.1,3.0,
Two tickets that warrant attention:
https://issues.apache.org/jira/browse/CASSANDRA-9557
https://issues.apache.org/jira/browse/CASSANDRA-9558
On Fri, Jun 5, 2015 at 2:15 PM, Jason Brown jasedbr...@gmail.com wrote:
+1
On Friday, June 5, 2015, Sylvain Lebresne sylv...@datastax.com wrote:
+1
15 matches
Mail list logo
