cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-1657) support in-memory column families
Date Wed, 12 Mar 2014 23:43:43 GMT

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

Edward Capriolo commented on CASSANDRA-1657:
--------------------------------------------

I was working on some thrift features, since i am no longer occupied with that i need something
to do with my free time. Please all add your ideas for the implementation of this feature.

> support in-memory column families
> ---------------------------------
>
>                 Key: CASSANDRA-1657
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1657
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Peter Schuller
>            Assignee: Edward Capriolo
>            Priority: Minor
>
> Some workloads are such that you absolutely depend on column families being in-memory
for performance, yet you most definitely want all the things that Cassandra offers in terms
of replication, consistency, durability etc.
> In order to semi-deterministically ensure acceptable performance for such data, Cassandra
could support in-memory column families. Such an in-memory column family would imply that
mlock() be used on sstables for this column family. On start-up and on compaction completion,
they could be mmap():ed with MAP_POPULATE (Linux specific) or else just mmap():ed + mlock():ed
in such a way as to otherwise guarantee it is in-memory (such as userland traversal of the
entire file).



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

Mime
View raw message