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 Mon, 01 Aug 2016 20:35:20 GMT

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

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

I was incorrect. JMXEnabledThreadPoolExecutor automatically sets core pool threads to max
if you only specify core pool threads. So I am running into some other pain point around memory
accounting unrelated to flushing performance.

> 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