[
https://issues.apache.org/jira/browse/CASSANDRA-4150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281744#comment-13281744
]
Vijay commented on CASSANDRA-4150:
----------------------------------
Before i go ahead with the complicated implementation (touching most of the
cache values), i did a smoke test and thought of sharing the results.
lgmac-vparthsarathy:cass vparthasarathy$ java
-javaagent:/Users/vparthasarathy/Documents/workspace/cassandraT11/lib/jamm-0.2.5.jar
-jar ~/Desktop/TestJamm.jar 100000000
Using reflection took: 25954
Using NativeCalculation took: 178
Using MemoryMeter took: 992
lgmac-vparthsarathy:cass vparthasarathy$
I used
https://github.com/twitter/commons/blob/master/src/java/com/twitter/common/objectsize/ObjectSizeCalculator.java
for reflection test.
> Looks like Maximum amount of cache available in 1.1 is 2 GB
> -----------------------------------------------------------
>
> Key: CASSANDRA-4150
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4150
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.0
> Reporter: Vijay
> Assignee: Vijay
> Attachments: 0001-CASSANDRA-4139-v2.patch, 0001-CASSANDRA-4150.patch,
> 0002-Use-EntryWeigher-for-HeapCache.patch,
> 0002-add-bytes-written-metric-v2.patch, concurrentlinkedhashmap-lru-1.3.jar
>
>
> The problem is that capacity is a Integer which can maximum hold 2 GB,
> I will post a fix to CLHM in the mean time we might want to remove the
> maximumWeightedCapacity code path (atleast for Serializing cache) and
> implement it in our code.
--
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
