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 Sat, 06 Jun 2015 11:50:00 GMT


Benedict commented on CASSANDRA-9558:

may be the problem

This logic makes sense on the server-side, since there is likely more useful work for the
server to do in the meantime, but on the client we're just delaying the server from getting
started on processing our requests. We should be batching, but not delaying. i.e. flushing
as soon as we have written all pending messages.

> Cassandra-stress regression in 2.2
> ----------------------------------
>                 Key: CASSANDRA-9558
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Alan Boudreault
>            Priority: Blocker
>         Attachments: 2.1.log, 2.2.log, CASSANDRA-9558-2.patch, CASSANDRA-9558-ProtocolV2.patch,
atolber-CASSANDRA-9558-stress.tgz, 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, stress-2.2-java-driver-2.2.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