[ 
https://issues.apache.org/jira/browse/CASSANDRA-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075611#comment-14075611
 ] 

Robert Stupp edited comment on CASSANDRA-7438 at 7/27/14 12:18 PM:
-------------------------------------------------------------------

[~vijay2...@gmail.com] do you have a C* branch with lruc integrated? Or: what 
should I do to bring lruc+C* together? Is the patch up-to-date?

I've pushed a new branch 'native-plugin' with the changes for 
native-maven-plugin. It's separate from the other code. Works for Linux and OSX 
(depending on which machine the stuff's built). Windows stuff is bit more 
complicated - it doesn't compile. Have to dig a bit deeper. Maybe delay Win 
port...


was (Author: snazy):
[~vijay2...@gmail.com] do you have a C* branch with lruc integrated? Or: what 
should I do to bring lruc+C* together? Is the patch up-to-date?

I've pushed a new branch 'native-plugin' with the changes for 
native-maven-plugin - separate from the other code. Windows stuff is bit more 
complicated - it doesn't compile. Have to dig a bit deeper. Maybe delay Win 
port...

> Serializing Row cache alternative (Fully off heap)
> --------------------------------------------------
>
>                 Key: CASSANDRA-7438
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7438
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>         Environment: Linux
>            Reporter: Vijay
>            Assignee: Vijay
>              Labels: performance
>             Fix For: 3.0
>
>         Attachments: 0001-CASSANDRA-7438.patch
>
>
> Currently SerializingCache is partially off heap, keys are still stored in 
> JVM heap as BB, 
> * There is a higher GC costs for a reasonably big cache.
> * Some users have used the row cache efficiently in production for better 
> results, but this requires careful tunning.
> * Overhead in Memory for the cache entries are relatively high.
> So the proposal for this ticket is to move the LRU cache logic completely off 
> heap and use JNI to interact with cache. We might want to ensure that the new 
> implementation match the existing API's (ICache), and the implementation 
> needs to have safe memory access, low overhead in memory and less memcpy's 
> (As much as possible).
> We might also want to make this cache configurable.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to