cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-6969) Use Unsafe Mutations Where Possible in Unit Tests
Date Tue, 01 Apr 2014 21:16:28 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957020#comment-13957020
] 

Jonathan Ellis edited comment on CASSANDRA-6969 at 4/1/14 9:15 PM:
-------------------------------------------------------------------

We should look at it after CASSANDRA-6968, but for now batch CL doesn't look like a big contributor
to the slowness.  On my machine it's 12:25 with batch and 12:02 with periodic.


was (Author: jbellis):
We should look at it after CASSANDRA-6968, but for now it batch CL doesn't look like a big
contributor to the slowness.  On my machine it's 12:25 with batch and 12:02 with periodic.

> Use Unsafe Mutations Where Possible in Unit Tests
> -------------------------------------------------
>
>                 Key: CASSANDRA-6969
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6969
>             Project: Cassandra
>          Issue Type: Test
>          Components: Tests
>            Reporter: Tyler Hobbs
>            Assignee: Lyuben Todorov
>            Priority: Minor
>
> Since the test config uses the "batch" mode for the commitlog, safe writes are quite
slow.  In tests that don't rely on safe writes, we should use unsafe writes.  This mostly
consists of converting {{RowMutation.apply()}} calls into {{RowMutation.applyUnsafe()}} calls.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message