cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12228) Write performance regression in 3.x vs 3.0
Date Sat, 30 Jul 2016 01:49:20 GMT

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

Ariel Weisberg commented on CASSANDRA-12228:
--------------------------------------------

I think there is also an issue I am stilling working on nailing down where memory accounting
releases memory pinned by memtables too early or is just off by too much causing the heap
to fill up with memtables that are waiting for the post flush executor. I can see the heap
going to double the limit in a heap dump and things are falling apart server side.

> Write performance regression in 3.x vs 3.0
> ------------------------------------------
>
>                 Key: CASSANDRA-12228
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12228
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: T Jake Luciani
>            Assignee: Marcus Eriksson
>            Priority: Minor
>             Fix For: 3.9
>
>
> I've been tracking down a performance issue in trunk vs cassandra-3.0 branch.
> I think I've found it.  CASSANDRA-6696 changed the default memtable flush default to
1 vs the min of 2 in cassandra-3.0.
> I don't see any technical reason for this and we should add back the min of 2 sstable
flushers per disk.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message