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

Branimir Lambov edited comment on CASSANDRA-17240 at 10/20/22 8:33 AM:
-----------------------------------------------------------------------

The code has been rebased and squashed into 4 commits. Tests are running 
[here|https://app.circleci.com/pipelines/github/blambov/cassandra/265/workflows/15104f84-9e13-4c5e-9310-6d567483e8c1.].

Can you please take a quick look at the last commit, with added NEWS.txt, 
CHANGES.txt and docs?


was (Author: blambov):
The code has been rebased and squashed into 4 commits. Tests are running 
[here|[https://app.circleci.com/pipelines/github/blambov/cassandra/265/workflows/15104f84-9e13-4c5e-9310-6d567483e8c1].]

Can you please take a quick look at the last commit, with added NEWS.txt, 
CHANGES.txt and docs?

> CEP-19: Trie memtable implementation
> ------------------------------------
>
>                 Key: CASSANDRA-17240
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17240
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local/Memtable
>            Reporter: Branimir Lambov
>            Assignee: Branimir Lambov
>            Priority: Normal
>         Attachments: SkipListMemtable-OSS.png, TrieMemtable-OSS.png, 
> density_SG.html.gz, density_test_with_sharding.html.gz, latency-1_1-95.png, 
> latency-9_1-95.png, throughput_SG.png, throughput_apache.png
>
>          Time Spent: 13h 20m
>  Remaining Estimate: 0h
>
> Trie-based memtable implementation as described in CEP-19, built on top of 
> CASSANDRA-17034 and CASSANDRA-6936.
> The implementation is available in this 
> [branch|https://github.com/blambov/cassandra/tree/CASSANDRA-17240].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to