cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9558) Cassandra-stress regression in 2.2
Date Tue, 23 Jun 2015 23:10:44 GMT


Benedict commented on CASSANDRA-9558:

bq. That all said, some basic back-of-envelope maths suggest this cannot sufficiently account
for the problem in this case

It was a lengthy message but I already realised this could not explain it. Should have highlighted
it more, sorry.

I wonder if we could try playing with the {{ethtool -c}} settings on the C\* server, to see
if reducing the number of interrupts can help (by e.g. raising the rx-usecs setting). 

What size cluster are these tests being run against, for reference? If it's a single node,
I'm not actually very worried or perturbed by a reduction, although we should probably try
to mitigate the issue for benchmark purposes.

> Cassandra-stress regression in 2.2
> ----------------------------------
>                 Key: CASSANDRA-9558
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Alan Boudreault
>            Assignee: T Jake Luciani
>             Fix For: 2.2.x
>         Attachments: 2.1.log, 2.2.log, CASSANDRA-9558-2.patch, CASSANDRA-9558-ProtocolV2.patch,
atolber-CASSANDRA-9558-stress.tgz, atolber-trunk-driver-coalescing-disabled.txt, stress-2.1-java-driver-,
stress-2.1-java-driver-2.2+PATCH.log, stress-2.1-java-driver-2.2.log, stress-2.2-java-driver-2.2+PATCH.log,
> We are seeing some regression in performance when using cassandra-stress 2.2. You can
see the difference at this url:
> The cassandra version of the cluster doesn't seem to have any impact. 
> //cc [~tjake] [~benedict]

This message was sent by Atlassian JIRA

View raw message