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 2011/09/12 20:09:18 UTC

[jira] [Updated] (CASSANDRA-3183) Make SerializingCacheProvider the default if JNA is available

     [ https://issues.apache.org/jira/browse/CASSANDRA-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-3183:
--------------------------------------

    Attachment: 3183.txt

> Make SerializingCacheProvider the default if JNA is available
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-3183
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3183
>             Project: Cassandra
>          Issue Type: Task
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 1.0.0
>
>         Attachments: 3183.txt
>
>
> The serializing cache is a better choice for most users:
> - Lower total memory usage (serialized data is usually 8x-12x smaller than "live" data in the JVM with all the overhead that involves) means you can cache more rows for a given memory footprint
> - Moving the serialized rows off-heap means you can use smaller heaps, reducing the impact of GC pauses

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira