Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sun, 15 Apr 2012 00:53:17 +0000 (UTC)
From: "Christian Spriegel (Created) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <679464825.26061.1334451197255.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (CASSANDRA-4153) Optimize truncate when snapshots
 are disabled or keyspace not durable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Optimize truncate when snapshots are disabled or keyspace not durable
---------------------------------------------------------------------

                 Key: CASSANDRA-4153
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4153
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Christian Spriegel
            Priority: Minor


My goal is to make truncate to be less IO intensive so that my junit tests run faster (as already explained in CASSANDRA-3710). I think I have now a solution which does not change too much:

I created a patch that optimizes three things within truncate:
- Skip the whole Commitlog.forceNewSegment/discardCompletedSegments, if durable_writes are disabled for the keyspace.
- With CASSANDRA-3710 implemented, truncate does not need to flush memtables to disk when snapshots are disabled.
- Reduce the sleep interval

The patch works nicely for me. Applying it and disabling durable_writes/autoSnapshot increased the speed of my testsuite vastly. I hope I did not overlook something.

Let me know if my patch needs cleanup. I'd be glad to change it, if it means the patch will get accepted.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira