cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3183) Make SerializingCacheProvider the default if JNA is available
Date Mon, 12 Sep 2011 22:19:08 GMT


Pavel Yaskevich commented on CASSANDRA-3183:

bq. I don't think this is actually technically correct, though – JNA Memory does not require
libc to work.

we can still use Memory.class.getName() there if you like

> Make SerializingCacheProvider the default if JNA is available
> -------------------------------------------------------------
>                 Key: CASSANDRA-3183
>                 URL:
>             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
> 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:


View raw message