cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ariel Weisberg (JIRA)" <>
Subject [jira] [Comment Edited] (CASSANDRA-12228) Write performance regression in 3.x vs 3.0
Date Tue, 02 Aug 2016 01:45:20 GMT


Ariel Weisberg edited comment on CASSANDRA-12228 at 8/2/16 1:45 AM:


I set the default back to the calculation that existed before and updated the documentation.
I would like to remove memtable_cleanup_threshold scoped as part of this ticket. I can't see
why you would set that to anything other than the default calculation and removing it would
help offset the additional lines of doc for memtable_flush_writers.

Somewhat orthogonal regarding my earlier comments about too much memory utilization. I created
CASSANDRA-12358 for that.

was (Author: aweisberg):

> Write performance regression in 3.x vs 3.0
> ------------------------------------------
>                 Key: CASSANDRA-12228
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: T Jake Luciani
>            Assignee: Ariel Weisberg
>            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

View raw message