cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-3183) Make SerializingCacheProvider the default if JNA is available
Date Mon, 12 Sep 2011 22:43:09 GMT

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

Pavel Yaskevich updated CASSANDRA-3183:
---------------------------------------

    Attachment: CASSANDRA-3183-alt-v3.patch

You are absolutely right, I forgot to revert that but fixed now, v3 is re-attached.

> 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-additions.patch, 3183-alt.patch, 3183.txt, CASSANDRA-3183-alt-v2.patch,
CASSANDRA-3183-alt-v3.patch
>
>
> 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

        

Mime
View raw message