Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 26 Aug 2013 23:16:53 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12665445.1377483485262.35704.1377559013050@arcas>
In-Reply-To: <JIRA.12665445.1377483485262@arcas>
References: <JIRA.12665445.1377483485262@arcas>
Subject: [jira] [Commented] (CASSANDRA-5935) Allow disabling slab allocation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-5935:
-------------------------------------------

Committed to 1.2.10 and 2.0.1 (but not 2.0.0).
                
> Allow disabling slab allocation
> -------------------------------
>
>                 Key: CASSANDRA-5935
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5935
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 1.2.10, 2.0.1
>
>         Attachments: 5935.txt, 5935-v2.txt
>
>
> Arena allocation (CASSANDRA-2252) dramatically improves garbage collection performance, but it can limit the number of tables that can be practically defined in the schema since you have a minimum of 1MB of heap per table.
> Although having more than dozens or hundreds of tables defined is almost certainly a Bad Idea (just as it is a design smell in a relational database), it's relatively straightforward to allow disabling the SlabAllocator.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira