You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/08/26 04:20:51 UTC

[jira] [Commented] (CASSANDRA-5935) Allow disabling slab allocation

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

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

Note that I've deliberately omitted this setting from cassandra.yaml; see above on "almost certainly a Bad Idea."
                
> 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.9
>
>         Attachments: 5935.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