You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "shylaja kokoori (JIRA)" <ji...@apache.org> on 2019/01/14 23:53:00 UTC
[jira] [Commented] (CASSANDRA-13981) Enable Cassandra for
Persistent Memory
[ https://issues.apache.org/jira/browse/CASSANDRA-13981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16742600#comment-16742600 ]
shylaja kokoori commented on CASSANDRA-13981:
---------------------------------------------
We have a new implementation of the [persistent memory storage engine|https://github.com/shyla226/cassandra/tree/13981_llpl_engine] based on the design and sketch that [~jasobrown] proposed. This implementation uses an improved version of [LLPL|https://github.com/pmem/llpl]. As suggested in Jason's design, this engine uses the Adaptive Radix Tree as the core data structure. Also, as suggested, it uses the default Cassandra serialization / deserialization code.
The engine implements creates, reads, updates, deletes, and table schema modification. We have tested these features on a single node using the insanity schema with > 2 billion partitions.
We would like to get feedback on the storage engine and guidance from the Cassandra community on next steps. In particular, we have implemented placeholder read path code because the pluggable storage engine read path API is not yet resolved (https://issues.apache.org/jira/browse/CASSANDRA-14117).
> Enable Cassandra for Persistent Memory
> ---------------------------------------
>
> Key: CASSANDRA-13981
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13981
> Project: Cassandra
> Issue Type: New Feature
> Components: Legacy/Core
> Reporter: Preetika Tyagi
> Assignee: Preetika Tyagi
> Priority: Major
> Fix For: 4.x
>
> Attachments: in-mem-cassandra-1.0.patch, in-mem-cassandra-2.0.patch, in-mem-cassandra-2.1.patch, readme.txt, readme2.1.txt, readme2_0.txt
>
>
> Currently, Cassandra relies on disks for data storage and hence it needs data serialization, compaction, bloom filters and partition summary/index for speedy access of the data. However, with persistent memory, data can be stored directly in the form of Java objects and collections, which can greatly simplify the retrieval mechanism of the data. What we are proposing is to make use of faster and scalable B+ tree-based data collections built for persistent memory in Java (PCJ: https://github.com/pmem/pcj) and enable a complete in-memory version of Cassandra, while still keeping the data persistent.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org