[
https://issues.apache.org/jira/browse/CASSANDRA-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Yang updated CASSANDRA-3183:
---------------------------------
Comment: was deleted
(was: 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: 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
