cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yang Yang (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3183) Make SerializingCacheProvider the default if JNA is available
Date Fri, 30 Sep 2011 16:47:46 GMT


Yang Yang commented on CASSANDRA-3183:

I actually ran into some issues with the serializing cache, it seems to make the perm gen
unable to GC (even with a forced full GC), and increases memory consumption much faster.

I had to invoke invalidate cache in JMX followed by a forced GC to release that memory.

just a FYI for now, I'm still going through the tests and comparison with the hashmap-based
cache, will update more definitively when I get more results
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message