cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5935) Allow disabling slab allocation
Date Mon, 26 Aug 2013 02:20:51 GMT

    [ 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

Mime
View raw message